Clarify that GsonBuilder.setExclusionStrategies
does not replace existing ones (#2168)
* Clarify that `GsonBuilder.setExclusionStrategies` does not replace existing ones * Fix punctuation
This commit is contained in:
parent
246270e02c
commit
390385e382
|
@ -368,6 +368,8 @@ public final class GsonBuilder {
|
||||||
* deserialization. Each of the {@code strategies} will be applied as a disjunction rule.
|
* deserialization. Each of the {@code strategies} will be applied as a disjunction rule.
|
||||||
* This means that if one of the {@code strategies} suggests that a field (or class) should be
|
* This means that if one of the {@code strategies} suggests that a field (or class) should be
|
||||||
* skipped then that field (or object) is skipped during serialization/deserialization.
|
* skipped then that field (or object) is skipped during serialization/deserialization.
|
||||||
|
* The strategies are added to the existing strategies (if any); the existing strategies
|
||||||
|
* are not replaced.
|
||||||
*
|
*
|
||||||
* @param strategies the set of strategy object to apply during object (de)serialization.
|
* @param strategies the set of strategy object to apply during object (de)serialization.
|
||||||
* @return a reference to this {@code GsonBuilder} object to fulfill the "Builder" pattern
|
* @return a reference to this {@code GsonBuilder} object to fulfill the "Builder" pattern
|
||||||
|
|
Loading…
Reference in New Issue
Block a user