-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
Move the experimental 'category edition' button into the Edit mode #1683
Comments
Does the category edit mode work ok if we have no category at all ? |
No, the button "Edit" is deactivated, since nothing happens when the "Additional Button" is clicked in this case. If we have no category as all, the button "Add missing product category" is shown, but no action has been applied yet. |
@teolemon @cli1005 Actually the current implementation is more or less OK when you want to slightly fix an existing category. It does not work when you're starting from scratch, the reason being that we don't really have access to root categories:
Besides, as a user I'm not sure I would bother to climb the category tree step by step, where on the website I can just type "sardines à l'huile" instead of a painful exploration of Conserves, Produits de la mer, Poissons, Poissons en conserve, Poissons et viandes et oeufs, Sardines, Sardines en conserve, Filets de poissons, Sardines à l'huile, Filets de sardines, Sardines à l'huile d'olive, Sardine à l'huile d'olive appertisée |
We just add a button in the Product Edition page which works the same way as the "Additional Button", no change has been made to the Category Edition :) |
@teolemon Not sure I follow you: are we supposed to show this to an end-user that clicks on the "No category so far: please select one" button? |
@cli1005 It's just that in Category Edition there were cases that were not handled (cf. the |
Yes, we might need or have already another issue concerning TODOs of Category Edition? the objective of this issue is just to move the button, in my opinion |
|
@teolemon Could also be fixed if |
So... I create a PR juste for the new button or we wait for all the points to reach? |
I've updated my comment with links to the blocking issues. Let's put this one on hold, at least until we clean up server side ? |
Started the clean-up server side @cli1005 @monsieurtanuki @stephanegigandet |
@teolemon I can start working on the "No category: we start from root" feature, can't I? |
Two are equally valid and complementary options. |
@teolemon Have you got some starting point suggestions for the "type in/search category" feature? |
We have the autosuggest API in the Dart package already, and then on click, you could load the partial taxo API matching the selected tag (thus no UI change needed for final validation) |
@teolemon I know that's not what the mocks said but my brain does not understand the concept of multiple categories on the same tree, UI/UX-wise. I suggest something similar to the website: the list of the current product categories, and the possibility to add a category with autocomplete. |
I'm not sure I understand how I'm supposed to interact with this new mockup. At this point of complexity, the solution we have in V1 (field with existing categories as chips, plus the ability to add more thanks to autocomplete) looks more intuitive. |
@monsieurtanuki I've made variants with Radio buttons, but I do believe multiple category selection should remain possible. The second one is in line with the idea that you'd have to pick just one category (removing the list of currently existing categories on a product). |
Also, in the case of single category selection, I'm not sure how we're supposed to handle the thousands of products who do have multiple categories. |
@teolemon Would you prefer something like this? |
According to https://openfoodfacts.github.io/api-documentation/#7Metadata
@teolemon That would tend to plead for "type in keywords/search" rather than "tree search", wouldn't it? |
Probably. |
Closing for now, let's focus on adding autocompletion to the current view. |
What
Mockup
Part of
The text was updated successfully, but these errors were encountered: