Add support for omitting defaults #269
Conversation
If a class is annotated with the new `@OmitDefaults` annotation, which requires a builder, then all properties that have a value set by the default builder method and correspond to a getter function on the builder have their value omitted from the serialized JSON if it matches the default one.
|
@rharter A bit of context: This came up over at Bazel while building some kind of generic package manager that heavily relies on auto-value-gson to generate its lockfile. Since we also need to hash the contents of these lockfiles and want them to remain stable as we add new fields, we need some way to omit fields that are at their default values. The approach taken in this PR felt natural to me, but I am open to suggestions to do this differently. I also think that #268 could be solved by this as well in a backwards compatible way: Omit |
1 participant
If a class is annotated with the new
@OmitDefaultsannotation, which requires a builder, then all properties that have a value set by the default builder method and correspond to a getter function on the builder have their value omitted from the serialized JSON if it matches the default one.