Created by: bodograumann
Currently the deserializer fills all fields which are missing in the payload with the value undefined. Usually the difference between a missing field and a field which is set to undefined is not important. In some cases the behaviour is different however. For example when using Object.keys, the in operator or a strict recursive comparison like lodash’s isEqual.
This PR changes the behaviour, so that the missing fields are skipped and the deserialized objects do not have them set to undefined anymore.
I feel this is the correct approach, because this is the most strict meaning for optional properties in typescript. (Even though the flag that checks strictly is not enabled by default, for backward compatibility.)
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. -
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 @TiFu (2017/07) @taxpon (2017/07) @sebastianhaas (2017/07) @kenisteward (2017/07) @Vrolijkx (2017/09) @macjohnny (2018/01) @topce (2018/10) @akehir (2019/07) @petejohansonxo (2019/11) @amakhrov (2020/02) @davidgamero (2022/03)