-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use search #2235
Use search #2235
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
We ensure that for every entry that is a match we _always_ provide tokens. This ensures that a user can rely on these tokens being there, i.e. to render the results. Related to bpmn-io/bpmn-js#2235
This ensures we properly handle fuzzy results (again), i.e. when providing multiple search strings, return results that match on a best effort basis, rather than being overly strict: items = [ 'foo', 'bar' ] search = 'foo bar' result = [ 'foo', 'bar' ] The tokens allow folks to make sense of the actual parts of the results matched, and allow them to refine the search as they see fit. Along with this results are still scored, i.e. most reasonable results are first shown to the users. Related to bpmn-io/bpmn-js#2235
We ensure that for every entry that is a match we _always_ provide tokens. This ensures that a user can rely on these tokens being there, i.e. to render the results. Related to bpmn-io/bpmn-js#2235
This ensures we properly handle fuzzy results (again), i.e. when providing multiple search strings, return results that match on a best effort basis, rather than being overly strict: items = [ 'foo', 'bar' ] search = 'foo bar' result = [ 'foo', 'bar' ] The tokens allow folks to make sense of the actual parts of the results matched, and allow them to refine the search as they see fit. Along with this results are still scored, i.e. most reasonable results are first shown to the users. Related to bpmn-io/bpmn-js#2235
We ensure that for every entry that is a match we _always_ provide tokens. This ensures that a user can rely on these tokens being there, i.e. to render the results. Related to bpmn-io/bpmn-js#2235
This ensures we properly handle fuzzy results (again), i.e. when providing multiple search strings, return results that match on a best effort basis, rather than being overly strict: items = [ 'foo', 'bar' ] search = 'foo bar' result = [ 'foo', 'bar' ] The tokens allow folks to make sense of the actual parts of the results matched, and allow them to refine the search as they see fit. Along with this results are still scored, i.e. most reasonable results are first shown to the users. Related to bpmn-io/bpmn-js#2235
Upstream fixes most described isses: bpmn-io/diagram-js#932. Try out the changes via
CC @lmbateman |
This ensures we properly handle fuzzy results (again), where parts of the search is matched across different keys. This ensures we're not overly strict in filtering things. Related to bpmn-io/bpmn-js#2235
This ensures we properly handle fuzzy results (again), where parts of the search is matched across different keys. This ensures we're not overly strict in filtering things. Related to bpmn-io/bpmn-js#2235
We ensure that for every entry that is a match we _always_ provide tokens. This ensures that a user can rely on these tokens being there, i.e. to render the results. Related to bpmn-io/bpmn-js#2235
This ensures we properly handle fuzzy results (again), where parts of the search is matched across different keys. This ensures we're not overly strict in filtering things. Related to bpmn-io/bpmn-js#2235
We ensure that for every entry that is a match we _always_ provide tokens. This ensures that a user can rely on these tokens being there, i.e. to render the results. Related to bpmn-io/bpmn-js#2235
This ensures we properly handle fuzzy results (again), where parts of the search is matched across different keys. This ensures we're not overly strict in filtering things. Related to bpmn-io/bpmn-js#2235
We ensure that for every entry that is a match we _always_ provide tokens. This ensures that a user can rely on these tokens being there, i.e. to render the results. Related to bpmn-io/bpmn-js#2235
This ensures we properly handle fuzzy results (again), where parts of the search is matched across different keys. This ensures we're not overly strict in filtering things. Related to bpmn-io/bpmn-js#2235
Previous observations, addressed by this PR as well as bpmn-io/diagram-js#932: Some observations:
Overall we can see that this is quite an improvement, removing the heavy matching / tokenization from implementors. Great job 🎖️ |
This ensures we build upon the new search abstraction, built via bpmn-io/diagram-js#916.
Integrates improved search. Cf. https://github.com/bpmn-io/diagram-js/blob/develop/CHANGELOG.md#1510
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff! Glad to see this in bpmn-js finally! 🥇
Proposed Changes
This plugs into the new
search
utility shipped with bpmn-io/diagram-js#916 / [email protected], now updated and fixed via bpmn-io/diagram-js#932:Try out via
Checklist
To ensure you provided everything we need to look at your PR:
@bpmn-io/sr
toolCloses {LINK_TO_ISSUE}
orRelated to {LINK_TO_ISSUE}
Depends on bpmn-io/diagram-js#932