-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JsonDecoder should take into account all annotations on EnumN
and GenericRecord
#700
Labels
Comments
/bounty $250 |
💎 $250 bounty • ZIOSteps to solve:
Thank you for contributing to zio/zio-schema! Add a bounty • Share on socials
|
/attempt #700
|
987Nabil
added a commit
to 987Nabil/zio-schema
that referenced
this issue
Jun 29, 2024
💡 @987Nabil submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
987Nabil
added a commit
to 987Nabil/zio-schema
that referenced
this issue
Jun 30, 2024
987Nabil
added a commit
to 987Nabil/zio-schema
that referenced
this issue
Jun 30, 2024
jdegoes
pushed a commit
that referenced
this issue
Jul 9, 2024
🎉🎈 @987Nabil has been awarded $250! 🎈🎊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
enumEncoder/Decoder
and therecordEncoder/Decoder
almost ignore all annotations on fields. Something like mapped names with the@fieldName
annotation are working, because they are picked up by the macro and set as name of the fields. But we should not rely on it. If I create a Schema by hand and add the annotation or add the annotation after the macro, it should still work.The text was updated successfully, but these errors were encountered: