You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A very common need that is not currently supported is the ability to insert additional properties in JSON (etc) output, without requiring physical POJO properties. This could include things like:
Injecting custom BeanPropertyWriter instances (or perhaps a new sub-type), giving more control
Now; although there are some existing annotations that could work her (@JsonSerialize, specifically, from databidn package), it might make sense to add a new annotation or annotations.
Some things to consider:
How to specify ordering of these attributes? While @JsonPropertyOrder needs to take these into account, it'd make sense to at least specify "default" placement before or after "regular" properties.
For attributes, should name of attribute be 1-to-1 with property name to use? (fine as default, but if/how to allow override?)
How to minimize amount of annotation decorations to use, without exploding number of annotations; esp. considering need to support (1) and ()
The text was updated successfully, but these errors were encountered:
(note: replaces #322; possibly addresses #274)
A very common need that is not currently supported is the ability to insert additional properties in JSON (etc) output, without requiring physical POJO properties. This could include things like:
BeanPropertyWriter
instances (or perhaps a new sub-type), giving more controlNow; although there are some existing annotations that could work her (
@JsonSerialize
, specifically, from databidn package), it might make sense to add a new annotation or annotations.Some things to consider:
@JsonPropertyOrder
needs to take these into account, it'd make sense to at least specify "default" placement before or after "regular" properties.The text was updated successfully, but these errors were encountered: