docs: changelog 1.2.1/1.3.1, deps bumps, flowchart Arrange clarity - #10
Conversation
Mirror package highlights so the site changelog stays current with the published line (glass modal, chrome fixes, Arrange select polish). Co-authored-by: Cursor <cursoragent@cursor.com>
Include the already-applied patch bumps for the docs-site toolchain. Co-authored-by: Cursor <cursoragent@cursor.com>
Document Tree/Radial/Grid (no placeholder), sync the mind-map demo to radial on ready, and regression-test the arrange select options. Co-authored-by: Cursor <cursoragent@cursor.com>
Nudge hero .vd-btn-ring inner/outer strokes from 2px to 1.5px so the double outline reads lighter on the dark hero without changing gap or collision-safe offsets. Co-authored-by: Cursor <cursoragent@cursor.com>
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| so 100% + margin does not make neighboring rings collide. */ | ||
| .hero-cta-buttons .vd-btn-outline.vd-btn-ring { | ||
| border-width: 2px; | ||
| border-width: 1.5px; |
There was a problem hiding this comment.
SUGGESTION: Sub-pixel border-width (1.5px) renders inconsistently across browsers.
Fractional pixel values for border-width are handled differently by each engine — some round to 1px, others to 2px, and others render true sub-pixel borders. The intended "thinner" look may not materialize consistently. Consider using 1px or 2px for reliable cross-browser rendering, or test thoroughly in Chrome, Firefox, and Safari.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| onBeforeUnmount(exitFullscreen); | ||
|
|
||
| /** Align Arrange with the mind-map seed (Tree/Radial/Grid — three modes). */ | ||
| function onFlowchartReady(editor: { layout?: (mode?: string) => unknown }) { |
There was a problem hiding this comment.
SUGGESTION: Potential viewport misalignment after layout("radial") without a subsequent fitView().
The auto-fit prop fits the viewport on initial load, and @ready fires after. Calling layout("radial") rearranges all node positions, but the viewport may not re-fit afterward — the nodes could end up outside the visible area or appear off-center. Consider calling a fitView() equivalent after layout() if the component does not re-fit automatically after layout changes.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Previous Review Summary (commit cb06fb7)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit cb06fb7)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (6 files)
Reviewed by deepseek-v4-pro · Input: 32K · Output: 3.9K · Cached: 241.8K |
Co-authored-by: Cursor <cursoragent@cursor.com>
1 participant
Summary
@vanduo-oss/vd31.2.1 and@vanduo-oss/vd3-cbun1.3.1 cards to the docs changelog (glass modal, spinner/spotlight/morph/button-group/transfer/collections/stepper; flowchart dark chrome, icon toolbar, Arrange select, short-parent sizing).@playwright/test,@types/node,eslint,eslint-plugin-vue,prettier,stylelint,vite,vue-tsc).Test plan
/changelog— Latest badges on vd3 1.2.1 and cbun 1.3.1; prior cards still present/canvas/flowchart— Arrange shows Radial after load; dropdown lists exactly Tree / Radial / Gridpnpm exec vue-tsc --noEmitandpnpm exec vitest run tests/unit/flowchart.spec.ts(already green locally)Made with Cursor