Conversation
chilagrow
left a comment
chilagrow
left a comment
There was a problem hiding this comment.
Thanks for providing the example, it show cases the simplicity 😃
Was there a reason for having choice for builder and interface option? Perhaps your have experience from maintaining operator code bases.
| 2. **Do we expect most providers to be simple or complex?** | ||
| 3. **How important is unit testing individual steps?** | ||
| 4. **Should we support both, or pick one to reduce maintenance burden?** | ||
| 5. **Is the hybrid approach a good compromise?** |
There was a problem hiding this comment.
- Interface feels more natural
- If existing providers are simple, I assume most providers would be simple and vice versa.
- I prefer integration tests, I would often avoid unit tests for the preference of integration tests 😅
- Let's pick one to reduce maintenance burden
- I don't think hybrid is necessary, particularly not at the start.
To be honest, we were just exploring options to make this as simple and easy to understand as possible and we came up with both approaches. |
examples/README.md
Outdated
| ## 📁 File Structure | ||
|
|
||
| ``` | ||
| examples/ |
There was a problem hiding this comment.
When we create a provider for production usage such as PSMDB, which repository would it be implemented in? 🤔
There was a problem hiding this comment.
My suggestion would be to have a separate repository for each provider
2 participants
No description provided.