fix(types): add zIndex as valid AxisType, remove CategoricalChartOptions assertions#3108
Merged
Merged
Conversation
neefrehman
changed the title
ckifer
approved these changes
Dec 19, 2022
ckifer
left a comment
ckifer
left a comment
Member
There was a problem hiding this comment.
LGTM, thanks for separating these changes
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-on from #3103
Adds 'zIndex' to the AxisType union type, which means we can avoid the type
assertion in
ComposedChart.tsxandScatterChart.tsx.I've also removed the unnecessary type assertion to
CategoricalChartOptionsin other chart components, which should improve type safety a little.