[Auto release] release 2.0.22#4556
Merged
xuefei1313 merged 22 commits intomainfrom Apr 13, 2026
Merged
Conversation
Sync main v2.0.21 to develop
chore: add unpkgFiles field to package.json for better CDN support
Feat: boxplot linear x-axis
…xtensionMark interactive states
- Remove afterStateUpdate event binding on individual graphics - Sync states directly in afterRender callback - Remove _bindHandlers, dedup markers - Add clearStates() for empty state scenario - Improve type safety with IMarkGraphic - Fix test page debug log
fix: fix bug of _reSetRenderState when release
…sionMarkSyncStatePlugin - Cache subscribed event instance (_subscribedEvent) to guard against redundant on/off calls when onAfterInitChart is invoked multiple times within the same chart lifecycle (e.g. updateModelSpec, setCurrentTheme) - Replace closure-captured service param with this.service from BasePlugin - Pre-filter syncable extensionMark specs before passing to _syncSeriesStates, eliminating the duplicate guard inside the forEach loop - Replace unsafe any types with IEvent and ISeriesSpec
…e-plugin feat: add ExtensionMarkSyncStatePlugin for vchart-extension
The Sankey tooltip helper treated source=0 as falsy, so link tooltips for the first indexed source skipped the expected "A => B" title. Add a regression test for the zero-index case and record the package changefile. Constraint: Sankey links can reference nodes by numeric index including 0 Rejected: Coerce source/target to strings before checks | still obscures the real bug Confidence: high Scope-risk: narrow Reversibility: clean Directive: Use nil checks for Sankey source/target presence instead of truthiness checks Tested: npm test -- --runInBand __tests__/unit/series/sankey.test.ts; npm run compile Not-tested: Browser hover interaction in the runtime playground
fix: preserve Sankey tooltip titles for zero-index source links
Stacked bar clip paths recomputed aggregate bounds from stack values even when barMinHeight had already rewritten the rendered segment geometry. Use the precomputed RECT coordinates for clip path bounds in that case and lock the regression with a chart unit test plus a Rush changefile. Constraint: barMinHeight rewrites rendered stack segment bounds before clipping Rejected: Disable stackCornerRadius when barMinHeight is set | drops intended styling Confidence: high Scope-risk: narrow Reversibility: clean Directive: When stack geometry is precomputed, derive clip bounds from RECT fields Tested: npm test -- --runInBand __tests__/unit/chart/bar.test.ts; npm run compile Not-tested: Browser rendering in the public playground for issue #4543
Tooltip theme merging was flattening nested style values and dropping root tooltip config such as mark and dimension visibility. This keeps style fields in spec.style, merges functional tooltip config at the root, and adds a focused regression for theme-driven tooltip visibility. Constraint: Tooltip themes must support both style fields and root spec fields Rejected: Fix only style merging | mark and dimension visibility would still be ignored Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep tooltip theme merge split between style keys and root spec keys Tested: Direct transformer probes for style nesting and mark visibility exclusion Tested: File-level TypeScript diagnostics on changed files Not-tested: Full package compile blocked by pre-existing continuous legend type errors
…r-radius fix: correct stack corner clipping with barMinHeight
fix: preserve tooltip theme visibility overrides
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
5 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.
This PR merges release branch release/2.0.22 into main.