dependabot[bot] opened a new pull request, #41276: URL: https://github.com/apache/superset/pull/41276
Bumps [react-arborist](https://github.com/jameskerr/react-arborist) from 3.10.1 to 3.10.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jameskerr/react-arborist/releases">react-arborist's releases</a>.</em></p> <blockquote> <h2>v3.10.5</h2> <p><strong>Fixes</strong></p> <ul> <li><code>TreeApi</code> methods (<code>select</code>, <code>focus</code>, <code>delete</code>, <code>edit</code>, node creation, etc.) now honor a custom <code>idAccessor</code> when given raw row data, instead of always reading <code>.id</code>. The identifier parameters and the <code>onCreate</code> return type accept your data type, so a custom accessor works end-to-end. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/366">#366</a>)</li> </ul> <h2>v3.10.4</h2> <p><strong>Fixes</strong></p> <ul> <li><code>initialData</code> now honors <code>idAccessor</code> and <code>childrenAccessor</code> (issue <a href="https://redirect.github.com/jameskerr/react-arborist/issues/73">#73</a>, also <a href="https://redirect.github.com/jameskerr/react-arborist/issues/170">#170</a>). The built-in data controller behind <code>initialData</code> hardcoded <code>id</code> and <code>children</code>, so trees keyed differently couldn't be reordered (drag ids never matched) and moving a node with children dropped them. The controller now reads ids and children through the same accessors as the rest of the tree. A string <code>childrenAccessor</code> is fully supported for reorder/create/delete; a function <code>childrenAccessor</code> is read-only, so write-back falls back to the <code>children</code> key. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/365">#365</a>)</li> </ul> <h2>v3.10.3</h2> <p><strong>Fixes</strong></p> <ul> <li>A node can no longer be dragged while it's being renamed (issue <a href="https://redirect.github.com/jameskerr/react-arborist/issues/195">#195</a>). Previously, dragging inside the rename input picked the row up and moved it — visible even in the official Gmail demo. The drag source now refuses to start a drag while the node is in editing state, matching the VS Code explorer. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/364">#364</a>)</li> </ul> <h2>v3.10.2</h2> <p><strong>Fixes</strong></p> <ul> <li>Dropping a dragged node in the empty area below the last row fires <code>onMove</code> again (issue <a href="https://redirect.github.com/jameskerr/react-arborist/issues/313">#313</a>). The drop logic had been moved into the per-row drop hook but never added to the outer (bottom-of-list) drop target, so drops to the very bottom of the tree were silently ignored. The shared handler now lives on <code>tree.drop()</code> and is used by both drop targets. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/361">#361</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jameskerr/react-arborist/blob/main/CHANGELOG.md">react-arborist's changelog</a>.</em></p> <blockquote> <h1>Version 3.10.5</h1> <p><strong>Fixes</strong></p> <ul> <li><code>TreeApi</code> methods (<code>select</code>, <code>focus</code>, <code>delete</code>, <code>edit</code>, node creation, etc.) now honor a custom <code>idAccessor</code> when given raw row data, instead of always reading <code>.id</code>. The identifier parameters and the <code>onCreate</code> return type accept your data type, so a custom accessor works end-to-end. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/366">#366</a>)</li> </ul> <h1>Version 3.10.4</h1> <p><strong>Fixes</strong></p> <ul> <li><code>initialData</code> now honors <code>idAccessor</code> and <code>childrenAccessor</code> (issue <a href="https://redirect.github.com/jameskerr/react-arborist/issues/73">#73</a>, also <a href="https://redirect.github.com/jameskerr/react-arborist/issues/170">#170</a>). The built-in data controller behind <code>initialData</code> hardcoded <code>id</code> and <code>children</code>, so trees keyed differently couldn't be reordered (drag ids never matched) and moving a node with children dropped them. The controller now reads ids and children through the same accessors as the rest of the tree. A string <code>childrenAccessor</code> is fully supported for reorder/create/delete; a function <code>childrenAccessor</code> is read-only, so write-back falls back to the <code>children</code> key. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/365">#365</a>)</li> </ul> <h1>Version 3.10.3</h1> <p><strong>Fixes</strong></p> <ul> <li>A node can no longer be dragged while it's being renamed (issue <a href="https://redirect.github.com/jameskerr/react-arborist/issues/195">#195</a>). Previously, dragging inside the rename input picked the row up and moved it — visible even in the official Gmail demo. The drag source now refuses to start a drag while the node is in editing state, matching the VS Code explorer. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/364">#364</a>)</li> </ul> <h1>Version 3.10.2</h1> <p><strong>Fixes</strong></p> <ul> <li>Dropping a dragged node in the empty area below the last row fires <code>onMove</code> again (issue <a href="https://redirect.github.com/jameskerr/react-arborist/issues/313">#313</a>). The drop logic had been moved into the per-row drop hook but never added to the outer (bottom-of-list) drop target, so drops to the very bottom of the tree were silently ignored. The shared handler now lives on <code>tree.drop()</code> and is used by both drop targets. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/361">#361</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jameskerr/react-arborist/commit/b02213647b9f9a2415b0ae7830cf8496fba27aa2"><code>b022136</code></a> v3.10.5</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/cc7a26cbc45ccad7431d4352d8a6737dbe023ebb"><code>cc7a26c</code></a> Honor custom idAccessor in TreeApi methods (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/347">#347</a>) (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/366">#366</a>)</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/444afdd5805c2e0e73ea9f72913b59f27fc30da3"><code>444afdd</code></a> v3.10.4</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/ef252df60533aa2b309042407576f95088861aff"><code>ef252df</code></a> Honor idAccessor/childrenAccessor with initialData (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/73">#73</a>) (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/365">#365</a>)</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/07fc69b7be05c6ccaee1e9db09a4165a287831fb"><code>07fc69b</code></a> v3.10.3</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/e4864deec029b2846ef02bc36ccd0b038da369c3"><code>e4864de</code></a> Disable dragging a node while it's being renamed (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/195">#195</a>) (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/364">#364</a>)</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/a0675dc2b9a8c34bd9de4b8a53d307e8b8b13f16"><code>a0675dc</code></a> v3.10.2</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/a848ee6a2f2ffbed27e5d5aa54fc43743ca1d3ca"><code>a848ee6</code></a> Sync main package.json to 3.10.1 and guard against version drift (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/363">#363</a>)</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/5a0f60dc3c95e22c9cb0e9d9e00679bb36a419c8"><code>5a0f60d</code></a> docs: sharpen changeset instructions in AGENTS.md (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/362">#362</a>)</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/4e94b87fdd178096247d46176110f8c090349f94"><code>4e94b87</code></a> Fire onMove when dropping below the last row (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/313">#313</a>) (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/361">#361</a>)</li> <li>Additional commits viewable in <a href="https://github.com/jameskerr/react-arborist/compare/v3.10.1...v3.10.5">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
