Fix victory-native/victory-zoom-container clipping bug #3026
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
Fixes #3022
Issue summary:
Previously, victory-native/victory-zoom-container spread the result of
useVictoryZoomContainer
intoVictoryContainer
Where the return type of
useVictoryZoomContainer
isBecause
VictoryContainer
received the entireprops
object as a prop, instead of spreading its properties, values such aswidth
andheight
wereundefined
- leading to the svg element to render with undefined values in itsviewBox
, e.g.thus clipping the rendered chart.
Solution:
Destructure the props/children result from
useVictoryContainer
and pass correctly toVictoryContainer
Additional changes:
to the demo/rn project to enable web browser debugging.
pnpm
instead ofyarn
and includebuild --watch
step for improved debuggingType of Change
How Has This Been Tested?
Ran rn/demo project, added
victory-zoom-container
to confirm before/after changes visually.Screenshots
Before
After
Checklist: (Feel free to delete this section upon completion)