-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support for custom serializers/deserializers #28
Labels
Comments
Would solve #27 . |
ledsoft
added a commit
that referenced
this issue
Apr 10, 2021
ledsoft
added a commit
that referenced
this issue
Apr 10, 2021
ledsoft
added a commit
that referenced
this issue
Apr 10, 2021
ledsoft
added a commit
that referenced
this issue
Apr 10, 2021
…lizer is used even when processing plural object property values.
ledsoft
added a commit
that referenced
this issue
Apr 10, 2021
Custom serializers support implemented in 0.8.7, basic documentation can be found on the Wiki. |
ledsoft
added a commit
that referenced
this issue
Mar 16, 2022
ledsoft
added a commit
that referenced
this issue
Mar 18, 2022
ledsoft
added a commit
that referenced
this issue
Mar 21, 2022
Add mechanism to retrieve property target type.
ledsoft
added a commit
that referenced
this issue
Mar 21, 2022
…perty value. Simplify DeserializationContext.
ledsoft
added a commit
that referenced
this issue
Mar 21, 2022
ledsoft
added a commit
that referenced
this issue
Mar 24, 2022
ledsoft
added a commit
that referenced
this issue
Mar 29, 2022
ledsoft
added a commit
that referenced
this issue
Mar 29, 2022
ledsoft
added a commit
that referenced
this issue
Mar 29, 2022
Add mechanism to retrieve property target type.
ledsoft
added a commit
that referenced
this issue
Mar 29, 2022
…perty value. Simplify DeserializationContext.
ledsoft
added a commit
that referenced
this issue
Mar 29, 2022
ledsoft
added a commit
that referenced
this issue
Mar 29, 2022
Implemented in 0.9.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a user, I sometimes find the default (de)serialization behavior of JB4JSON-LD unsuitable for my requirements. I want to be able to override the default behavior using my own (de)serializer. This overriding should be possible on class and field level.
Similar feature is available in Jackson via the
@JsonSerialize
and@JsonDeserialize
annotations.The text was updated successfully, but these errors were encountered: