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.
This PR allows end users to provide options to the way that type representations are constructed. This allows users to hook into the generic machinery and make the types match some alternate representation (say formatting based on aeson encoding rather than haskell representation).
Here is an example to Illustrate:
Here is my haskell type
I can build my bridge like so:
and this will output purescript like this:
This way my Haskell types can be the source of truth, but by modifying my aeson instances I can modify my purescript to be more idiomatic (no record field prefixes), and the JSON serialization / de-serialization stays in sync.