Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I'm constantly dealing with JSON documents which contain Java keywords or illegal characters I always have to work around this problem. This might not be a problem for a handful of classes but gets very time-consuming, error-prone and complex if you have to support multiple versions of a data exchange protocol or similar.
There have been several attempts to add per-property naming for DataObjects from different developers, but none of those made it to master.
With this Pull Request it would be possible to annotate a specific property like so:
The generated converter will then pick up the specified property name instead of the default one determined by the jsonPropertyNameFormatter.