This functionality would make sense to expose as part of the application. For example, we could place checkboxes next to the existing ingredient autosuggest fields.
Prompts/internationalization of the checkbox labels will be required.
Question: should the search results dynamically update when the checkbox values are updated by the user? We do this for the website-domain checkboxes, but they only appear post-search. Off the top of my head, I think it would be OK not to search-on-value-update for the dietary property checkboxes. It would be good to have clear product design guidance for this, however.
Describe the solution you'd like
Place checkboxes for each of the dietary properties in the unused space next to the ingredient search inputs
Pass the values of the checkboxes along to the recipe search API
Add server-side logging of dietary property filter selection
Is your feature request related to a problem? Please describe. The recipe search API supports filtering based on dietary properties.
This functionality would make sense to expose as part of the application. For example, we could place checkboxes next to the existing ingredient autosuggest fields.
Prompts/internationalization of the checkbox labels will be required.
Question: should the search results dynamically update when the checkbox values are updated by the user? We do this for the website-domain checkboxes, but they only appear post-search. Off the top of my head, I think it would be OK not to search-on-value-update for the dietary property checkboxes. It would be good to have clear product design guidance for this, however.
Describe the solution you'd like