Created by: janisz
Currently when we use gson builder all calls are connected with dot. This results in pretty long instruction that is problematic to parse for AST tools (e.g. lombok). To fix this we can slice this giant call into series of direct calls on named builder. As a result we get multiple short and easy to parse instructions instead of one long.
Fixes:
Refs:
- https://github.com/stackrox/jenkins-plugin/pull/158
- https://github.com/projectlombok/lombok/pull/3213
- https://github.com/projectlombok/lombok/issues/1118
- https://github.com/OpenAPITools/openapi-generator/pull/10875#discussion_r898263405
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master(6.0.1) (patch release),6.1.x(breaking changes with fallbacks),7.0.x(breaking changes without fallbacks) -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
cc: @bbdouglas @sreeshas @jfiala @lukoyanov @cbornet @jeff9finger @karismann @Zomzog @lwlee2608