TypeFromSelection Utility Type
#63
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
gksander
commented
Feb 16, 2023
Comment on lines
+256
to
257
| // @ts-expect-error data is unknown type since no grab present | ||
| expect("name" in data).toBeTruthy(); |
There was a problem hiding this comment.
I actually don't know how TS wasn't complaining about this prior to 4.9 🤔
carloskelly13
approved these changes
Feb 16, 2023
Merged
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.
This type will be handy-dandy, especially when extracting sub-queries/selections out into their own files and using their type in e.g. a React component's props. (Had to update some deps for TS
satisfiesoperator.)