InputGuesser - incomplete typing for reference input #562
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
|
Solved by giving ReferenceInput props as outer intersection, so now tests passes. However semantically previous commit (c75dfc5) looked more accurate to me, but then tests fails with "Property 'sort' does not exists" (?). |
adguernier
approved these changes
Jun 24, 2024
|
Merging this PR broke the |
|
this was green before merging |
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.
Adds missing types to InputGuesserProps to allow usage of ReferenceInput/ ReferenceInputArray extra props (ex.
sortorfilter).However test case still fails with (updated, see below):
Am I missing something (?)... I will come back to it when I have more time to dig it.
Fix: #561