-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Allow inverting @JsonProperty(access=)
with MapperFeature.INVERSE_READ_WRITE_ACCESS
so it can work differently on server side and client side
#2951
Comments
Nothing to support it out-of-the-box, but you should be able to sub-class Or, alternatively, use mix-in annotations (but that may be more work for larger sets of types). |
@JsonProperty(access=)
so it can work differently on server side and client side
@JsonProperty(access=)
so it can work differently on server side and client side@JsonProperty(access=)
so it can work differently on server side and client side
@JsonProperty(access=)
so it can work differently on server side and client side@JsonProperty(access=)
so it can work differently on server side and client side
@JsonProperty(access=)
so it can work differently on server side and client side@JsonProperty(access=)
with MapperFeature.INVERSE_READ_WRITE_ACCESS
so it can work differently on server side and client side
Implemented by addition of |
Implemented for 2.19.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@JsonProperty's access mode should be inversed on server side and client side when both sides are sharing the same module class.
when using access = READ_ONLY with @JsonProperty, on the server side, that means property need to be serialized but can't be deserialized. but on the client side, the same property should be able to be deserialized but not to be serialized.
Is it good to have an out-of-box feature to do this inversion?
The text was updated successfully, but these errors were encountered: