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
For simplicity (and because of the restraint on our Dto models) I implemented this using the fields, as the naming of the flowtype fields would be given without translation. But as you point out we should match Jackson in functionality and use the getters as a basis instead. Lets add a flag for selecting which you would want to use.
Currently, the main focus for generated fields in types is the Java field. But consider the following Java class:
then usually (at least when using Jackson API), instances of that class will result in JSON like this:
However, as there is no field
name
in classUser
, the resulting type will not include the name field:The text was updated successfully, but these errors were encountered: