v2.4.0: Migrate to Cloudflare Workers + feature additions#164
Merged
Conversation
Added collapsed-by-default "Needed Ingredients" sections to cooking and crafting pages with support for filtering by recipe state and season. **Motivation and goals:** Crafting every item requires a tremendous number of ingredients, some of which can only be obtained in certain seasons. Having a full list to reference makes it easy to plan ahead. Being able to filter by season makes near term planning much more tractable. **Features:** - Support for cooking and crafting recipes - Expands recipe ingredients recursively to make planning easier - Familiar card layouts with Wiki links - Custom Wiki links for non-specific ingredients (e.g. "Any Fish") - Filtering by known/unknown (crafted/cooked excluded to avoid clutter) - Filtering by season
Sorting of ingredients is done alphabetically by name and text search leverages the same patterns as text search in other areas. Co-authored-by: Denys Grybov <denys.grybov@hellofresh.com>
Fish have much more particular requirements for obtaining than crops and are not a shipping item in and of themselves (so season data was not being pulled). This commit brings in the information and displays from the Fishing page so that filtering fish by season works and information about catching them is readily available.
Used tabs for "All Recipes" and "Ingredient Tracker" as well as a prompt to show beta features to enable the "Ingredient Tracker"
The recent `FishSeet` modifications inadvertently hid the link to the wiki page when hiding buttons to set caught/uncaught state. This has been fixed.
The `BooleanCard` was the wrong thing to use in the `IngredientList` just to get the `FishSheet`. This unifies the usage paths for the list, but still opens the full panel for fish.
… Workers/OpenNext + remove Sentry observability
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
jacc
changed the title
jacc
changed the title
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
3 participants
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.
The majority of this PR is a structural change, catching up to the origin, and adding some small features requested by users.
New features:
Deployment/runtime: migrated to Cloudflare Workers via OpenNext.
Database access reworked for the Workers runtime.
The player patch API no longer uses raw SQL JSON_MERGE_PATCH. It now merges save updates in TypeScript before writing them back.
Auth/session handling cleaned up and centralized.
The app now reads the current user from /api/me (instead of the old /api entrypoint - this was for a CF Worker workaround)
Sentry integration removed. We weren't really actioning on any insights from them, and their instrumentation layer doesn't play nice with OpenNext.
Minor UI/component changes for type cleanup, fetch helper usage, and React 19 compatibility: