Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've talked to quite a few people about what we value in courier. The recurring themes are schema introspection and some distance from scala (i.e. rather than using straight case classes and tying ourselves even tighter to scala). I'll not recap all the problems/complaints with courier here (unless you'd like me to. Please let me know if that would be valuable.)
As an object of discussion, I'd like to propose the approach typified by the prototype below. Key characteristics of this approach worth reemphasizing are:
@backend="simple"
WithPrimitives.scala
toWithPrimitivesSimple.scala
)