fix(TS): no-index type to exclude [otherProp: string]: any; #1373
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.
Description
Final-form-api is using FormProps with
[otherProp: string]: any;
. If you then use Omit it will resolve in[otherProp: string]: any;
and all other types will not be visible anymore.Typescript playground
By using
NoIndex
we can exclude[otherProp: string]: any;
and have all the types that we normally have in FormProps.Related
Record
microsoft/TypeScript#50638Both of them are closed with some examples on how to fix it but it seems that the TypeScript team will not fix the Omit. 👎🏼
Checklist: (please see documentation page for more information)
Yarn build
passesYarn lint
passesYarn test
passesfix|feat({scope}): {description}
fix(pf3): wizard correctly handles next button
Fix button on documenation example page