This repository was archived by the owner on Nov 14, 2018. It is now read-only.
Removed generation of double Optionals for properties of Input type #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For objects of type
Input, the Swift code generation is creating unnecessary layers of Optionality for allOptionalproperties.Given this GraphQL input type
The code generated has two layers of Optionality. eg:
Optional<String?>This PR replaces to a single Optionality level, aligning with all other generated types.