Bump plutoprint from 0.19.0 to 0.20.0 in /app - #2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [plutoprint](https://github.com/plutoprint/plutoprint) from 0.19.0 to 0.20.0. - [Release notes](https://github.com/plutoprint/plutoprint/releases) - [Changelog](https://github.com/plutoprint/plutoprint/blob/main/docs/changelog.rst) - [Commits](plutoprint/plutoprint@v0.19.0...v0.20.0) --- updated-dependencies: - dependency-name: plutoprint dependency-version: 0.20.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Author
|
Superseded by #14. |
calreynolds
pushed a commit
that referenced
this pull request
Jul 27, 2026
- Particle/flow edges (biggest win): key EdgeFlow by edge id, not path, so a drag/resize updates the `path` attribute instead of unmounting + remounting the whole SMIL subtree every frame. Cut particle count 22→8. Suppress the animation entirely below 35% zoom (glyphs are sub-pixel there) via a primitive useStore(transform[2]) gate; the base line carries the edge. Total animated SVG elements ~halved. - Stabilise edgeOps (review #5): nodeRect/nodeAt/portsOf now read nodes from a nodesRef ([] deps) instead of closing over the live array, and use-edge-mutations takes nodesRef too — so the EdgeOpsContext value no longer churns every drag frame (was re-rendering every FlowEdge). - Memoise componentLookup(schema) once (review #4): the render-path `selected` lookup + the add/change-type callbacks reused it, rebuilding the whole catalog Map per frame. - Folded in nodeAt z-order tie-break (review nit): hit-test picks the topmost node by zIndex, not array order. O(E^2) fan-out hoist (review #2) left as documented backlog — negligible at the diagram's realistic edge counts and a riskier refactor. tsc + build clean. Verified live: 8 particles, dot=1 motion, zoom-out drops all flow then restores on zoom-in, no new console errors. Co-authored-by: Isaac
calreynolds
pushed a commit
that referenced
this pull request
Jul 27, 2026
Adversarial re-review of d3b9888 caught two issues in my own changes: 1. Reconnect preview/commit mismatch. Fix #2 added the `otherEnd` exclusion to the `move` (drag-preview) handler but NOT the `end` (commit) handler. So when the cursor was near both the other endpoint and a valid target, the preview snapped to the target while the commit resolved to the (nearer, excluded) other endpoint and silently dropped the reconnect. Apply the same exclusion in `end` so preview and commit agree. 2. computeLayout fallback ignored medallion params. The `naturalSize(n.type)` fallback in the resolve loop (used only when a node wasn't placed) didn't pass `n.params`, so it could under-size a forked medallion. Pass `n.params` to match the primary path. Also re-verified the other fixes against @xyflow/react internals: RowHandle → ConnectionDot is behaviour-preserving (source-type + ConnectionMode.Loose = both directions, as before; the dot is now screen-constant like every other anchor, which is the intended consistency, not a regression), and the isDocSource `isSource &&` gate can't drop a real case (no catalog component has a pdf/doc ICON; the pdf/doc conditions all imply isSource). Co-authored-by: Isaac
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
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.
Bumps plutoprint from 0.19.0 to 0.20.0.
Release notes
Sourced from plutoprint's releases.
Changelog
Sourced from plutoprint's changelog.
Commits
80dbcd0Release v0.20.08391e55Bump PlutoBook to v0.17.00d5b275Bump softprops/action-gh-release to v328af062Bump pypa/cibuildwheel to v3.4.13a13952Bump actions/download-artifact to v80ce315eBump actions/upload-artifact to v7Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)