backwards generic params compatibility #2933
Merged
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
Updated types to allow for either prop types in generic or the
ContainerType
to be inferred. This helps types remain backwards compatible with older types https://github.com/eatyourpeas/victory/blob/9a20d57c111023867bbdf1a9f3b4835acd76f4d3/packages/victory-create-container/src/index.d.ts#L4NOTE This isn't type safe. You can do
and it won't complain. This was true in the older versions too since it was attempting to type JavaScript. Inferring the types is definitely the better option. To the point where I am curious on if we should allow this behavior 🤨
Fixes # #2815
Type of Change
How Has This Been Tested?
Tested locally with old version
And new version
Also, you can do this too, this is what is inferred with new version
Checklist: (Feel free to delete this section upon completion)