dependabot[bot] opened a new pull request, #42689: URL: https://github.com/apache/superset/pull/42689
Bumps [react-arborist](https://github.com/jameskerr/react-arborist) from 3.15.1 to 3.16.0. <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.16.0</h2> <p><strong>Features</strong></p> <ul> <li>Added a <code>filteredCount</code> getter to the tree API, reporting how many nodes match the current <code>searchTerm</code> across the whole tree (regardless of which folders are open), or 0 when there is no active search. Consumers can now render a match count or a "no results" message via <code>isFiltered && filteredCount === 0</code> instead of inspecting <code>visibleNodes</code> (issues <a href="https://redirect.github.com/jameskerr/react-arborist/issues/112";>#112</a> and <a href="https://redirect.github.com/jameskerr/react-arborist/issues/256";>#256</a>). (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/383";>#383</a>)</li> </ul> <p><strong>Fixes</strong></p> <ul> <li>The default <code>searchMatch</code> no longer searches a node's children. It previously stringified every value of the node's data, the <code>children</code> array included, so each ancestor of a match counted as a match itself, and terms like <code>id</code> or <code>name</code> matched every folder by hitting keys nested in the children data. The filtered list is unchanged — parents of a match are still shown to keep the tree's structure — but <code>tree.filteredCount</code> now reports real matches. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/383";>#383</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.16.0</h1> <p><strong>Features</strong></p> <ul> <li>Added a <code>filteredCount</code> getter to the tree API, reporting how many nodes match the current <code>searchTerm</code> across the whole tree (regardless of which folders are open), or 0 when there is no active search. Consumers can now render a match count or a "no results" message via <code>isFiltered && filteredCount === 0</code> instead of inspecting <code>visibleNodes</code> (issues <a href="https://redirect.github.com/jameskerr/react-arborist/issues/112";>#112</a> and <a href="https://redirect.github.com/jameskerr/react-arborist/issues/256";>#256</a>). (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/383";>#383</a>)</li> </ul> <p><strong>Fixes</strong></p> <ul> <li>The default <code>searchMatch</code> no longer searches a node's children. It previously stringified every value of the node's data, the <code>children</code> array included, so each ancestor of a match counted as a match itself, and terms like <code>id</code> or <code>name</code> matched every folder by hitting keys nested in the children data. The filtered list is unchanged — parents of a match are still shown to keep the tree's structure — but <code>tree.filteredCount</code> now reports real matches. (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/383";>#383</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jameskerr/react-arborist/commit/d74c4ec696ba98c1a4e981075f6d60cdff3e290b";><code>d74c4ec</code></a> v3.16.0</li> <li><a href="https://github.com/jameskerr/react-arborist/commit/1277ac4b320ede5a616e242bc78a64566b8a7da2";><code>1277ac4</code></a> Add tree.filteredCount for search match count (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/112";>#112</a>, <a href="https://redirect.github.com/jameskerr/react-arborist/issues/256";>#256</a>) (<a href="https://redirect.github.com/jameskerr/react-arborist/issues/383";>#383</a>)</li> <li>See full diff in <a href="https://github.com/jameskerr/react-arborist/compare/v3.15.1...v3.16.0";>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]
