-
Notifications
You must be signed in to change notification settings - Fork 98
Added multiselection for categories and keywords to recipe editor #402
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
Added multiselection for categories and keywords to recipe editor #402
Conversation
272457c
to
2aecbec
Compare
@sam-19 Could you have a look at this? This PR touches only frontend parts. |
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.
From my perspective, this looks good. I just checked in a dev environment.
This is a good change. I don't have time to properly test it in a dev setting, but don't see anything apparently wrong with the changes. See my comment about using an implicit value prop in #386. |
2aecbec
to
aeed020
Compare
Codecov Report
@@ Coverage Diff @@
## master #402 +/- ##
========================================
Coverage 0.92% 0.92%
Complexity 410 410
========================================
Files 13 13
Lines 1300 1300
========================================
Hits 12 12
Misses 1288 1288
Flags with carried forward coverage won't be shown. Click here to find out more. |
Signed-off-by: Sebastian Fey <[email protected]>
Signed-off-by: Sebastian Fey <[email protected]>
Signed-off-by: Sebastian Fey <[email protected]>
… Added fallback in case loading kws or categories fails Signed-off-by: Sebastian Fey <[email protected]>
Signed-off-by: Sebastian Fey <[email protected]>
Signed-off-by: Sebastian Fey <[email protected]>
Signed-off-by: Sebastian Fey <[email protected]>
aeed020
to
9934bc2
Compare
This PR adds a NC-styled
Multiselect
element for keywords and categories for faster insertion.There is some collision with PR #386 but only for the keyword and category selection, which should be replaced by this one if accepted.
Closes #313 although for the future we might want to consider adding something similar for selecting ingredients, keywords, and tools as mentioned in the issue