fix: Use exact match for scraping first#892
Merged
TomBursch merged 2 commits intoTomBursch:mainfrom Oct 18, 2025
Merged
Conversation
Owner
|
Hi, thanks for tackling this! Since with order by the shortest names are listed first, which, if an exact name exists, is always that? |
24c2bf3 to
688f65a
Compare
TomBursch
approved these changes
Oct 18, 2025
…ring match and order results of partial match to make it predictable
01a876d to
ad0a8bd
Compare
Contributor
Author
|
Yes, you're right. This was redundant. |
w0s1nsk1
added a commit
to w0s1nsk1/kitchenowl
that referenced
this pull request
Feb 20, 2026
TomBursch#892) Co-authored-by: Tom Bursch <[email protected]>
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.
fix: try a exact match of scraped ingredients before using partial string match and order results of partial match to make it predictable
resolves #891