Repository navigation
chore: version canary packages (canary) - #604
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to canary, this PR will be updated.
canaryis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitoncanary.Releases
@bazza-ui/react@0.1.0-canary.18
Minor Changes
8deecbbThanks @kianbazza! - AddforceOrderMinScoreto data-first node defs (items, link items, tree items, radio and checkbox items, submenus, subpages). A row whose search score is below it sorts by score, as if it had noforceOrder, and still shows. Use it to lead with a row only when it matches well: withforceOrder: -1, forceOrderMinScore: 0.5, a "System" theme option leads for "sys" but no longer outranks "Settle" for "sett".forceScore, when set, is the score compared. Without it,forceOrderapplies to every match as before.Patch Changes
150bf4aThanks @kianbazza! - Data-first surfaces now use theirfilterprop. A customfilterscores rows in search and deep search, withforceScorestill taking precedence, where before every data-first search usedcommandScore.filter={false}turns filtering off: the surface shows its rows as it does with no search, which suitscontentyou filter yourself or a query loader that filters on the server.