frontend
internationalization
| frontend | internationalization | |
|---|---|---|
| 1 | 1 | |
| 12 | 0 | |
| - | - | |
| 8.0 | 10.0 | |
| 3 months ago | over 1 year ago | |
| TypeScript | Shell | |
| GNU Affero General Public License v3.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
frontend
-
Ask HN: Who needs help with side projects?
Thank you for the response!
> support splitting ingredients by typing a comma
That sounds sensible, yep; filed as https://github.com/openculinary/frontend/issues/210
> "Are there any ingredients that are not available?" ... I knew what you meant, the search will exclude recipes with those items, but it felt weird to read
That makes sense too. If I remember correctly, that prompt was most-recently rephrased during a pandemic-related lockdown (with subsequent unpredictable ingredient shortages), and so that context may have affected the choice of language; but I agree that it's odd phrasing and should be updated.
Hopefully that'll be a relatively quick correction, although it will require internationalization (currently machine-translated without review by native language speakers, not ideal); it's filed as https://github.com/openculinary/internationalization/issues/...
> box around the search form has a huge gap to the right of the form inputs
> I'd probably expect to see filters for vegan/veggie/pescatarian / low gi etc but then maybe not
Two good points here, and possibly combinable. Perhaps those dietary recipe filters could be placed in the excess space available next to the search controls.
Today the search API does theoretically support filtering[2] on a few dietary properties -- but that functionality isn't yet visible and available to the user.
Feature request filed as https://github.com/openculinary/frontend/issues/211
- Shopping list feature ... your icons seem too small and fiddly, and I'd want a few buttons on screen of common things - so I can tap those instead of typing
That sounds smart. This feature (and the meal planner) are under-attended relative to the recipe search/explore components, in my opinion. Let me think about this for a while, there are a few considerations and I'd like to be concise.
[2] - https://github.com/openculinary/api/blob/72075f66cd6fda5b809...
internationalization
-
Ask HN: Who needs help with side projects?
Thank you for the response!
> support splitting ingredients by typing a comma
That sounds sensible, yep; filed as https://github.com/openculinary/frontend/issues/210
> "Are there any ingredients that are not available?" ... I knew what you meant, the search will exclude recipes with those items, but it felt weird to read
That makes sense too. If I remember correctly, that prompt was most-recently rephrased during a pandemic-related lockdown (with subsequent unpredictable ingredient shortages), and so that context may have affected the choice of language; but I agree that it's odd phrasing and should be updated.
Hopefully that'll be a relatively quick correction, although it will require internationalization (currently machine-translated without review by native language speakers, not ideal); it's filed as https://github.com/openculinary/internationalization/issues/...
> box around the search form has a huge gap to the right of the form inputs
> I'd probably expect to see filters for vegan/veggie/pescatarian / low gi etc but then maybe not
Two good points here, and possibly combinable. Perhaps those dietary recipe filters could be placed in the excess space available next to the search controls.
Today the search API does theoretically support filtering[2] on a few dietary properties -- but that functionality isn't yet visible and available to the user.
Feature request filed as https://github.com/openculinary/frontend/issues/211
- Shopping list feature ... your icons seem too small and fiddly, and I'd want a few buttons on screen of common things - so I can tap those instead of typing
That sounds smart. This feature (and the meal planner) are under-attended relative to the recipe search/explore components, in my opinion. Let me think about this for a while, there are a few considerations and I'd like to be concise.
[2] - https://github.com/openculinary/api/blob/72075f66cd6fda5b809...
What are some alternatives?
baghchal.net - Online Baghchal Issue Tracker
rhino-pkg - A wrapper for apt + snap + flatpak + Pacstall
homebridge-lutron-caseta-leap - Homebridge support for Lutron Caseta Smart Bridge 2
infrastructure - This repository documents the steps required to set up a fresh RecipeRadar environment