Lines Matching +full:proguard +full:- +full:like
9 **Reason:** Your code is most likely not type-safe
13 - Avoid raw types: Instead of calling `fromJson(..., List.class)`, create for example a `TypeToken<…
14 See the [user guide](UserGuide.md#collections-examples) for more information.
15 - When using `TypeToken` prefer the `Gson.fromJson` overloads with `TypeToken` parameter such as [`…
16 The overloads with `Type` parameter do not provide any type-safety guarantees.
17 - When using `TypeToken` make sure you don't capture a type variable. For example avoid something l…
23 **Reason:** You use Gson by accident to access internal fields of third-party classes
29 …-in adapter for a type exists and no custom adapter has been registered, Gson falls back to using …
31 If you want to prevent using reflection on third-party classes in the future you can write your own…
39 - If the reported package is your own package then you have not configured the module declaration o…
40 - If the reported package is from a third party library or the JDK see [this troubleshooting point]…
42 **Solution:** Make sure the `module-info.java` file of your project allows Gson to use reflection o…
56 **Reason:** You probably have not configured ProGuard / R8 correctly
58 …ou have configured ProGuard / R8 correctly to preserve the names of your fields. See the [Android …
64 **Reason:** You probably have not configured ProGuard / R8 correctly; probably the fields names are…
66 …ou have configured ProGuard / R8 correctly to preserve the names of your fields. See the [Android …
70 …ProGuard and R8 produce a mapping file, this makes it easier to find out the obfuscated field name…
80 - is `static` (explicitly or implicitly when it is a top-level class)
81 - has a no-args constructor
95 - "double brace-initialization" also creates anonymous classes
96 - Local record classes (feature added in Java 16) are supported by Gson and are not affected by this
104 …leComplexMapKeySerialization()). See also the [user guide](UserGuide.md#maps-examples) for more in…
130 Note: Even in non-lenient mode Gson deviates slightly from the JSON specification, see [`JsonReader…
166 **Reason:** Gson by default omits JSON null from the output (or: ProGuard / R8 is not configured co…
170 … as JSON null, see the [related troubleshooting point](#null-values-for-anonymous-and-local-classe…
182 …-in adapter for a type exists and no custom adapter has been registered, Gson falls back to using …
184 If you want to prevent using reflection on third-party classes in the future you can write your own…