refactor(types): better null type handling #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use `null` literal to compose types intersections instead of using `NonNullable` for not nullable fields. It should lead to a lighter type definition. BREAKING CHANGE: Not sure if it really breaks anything but won't hurt to create a major version just in case. fix #33
3 tasks
|
Looks like a great clean up, and actual schema-to-code correspondence. By visually looking thru the changes I cannot spot any issues with it. Thanks a bunch! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use
nullliteral to compose types intersections instead of usingNonNullablefor not nullable fields. It should lead to a lighter type definition.BREAKING CHANGE: Not sure if it really breaks anything but won't hurt to create a major version just in case.
fix #33