rewrite get_all routes to use a pagination pattern to allow for better implementations of search, filter, and sorting on the frontend or by any client without fetching all the data. Additionally we added a CI check for running the Nuxt built to confirm that no TS errors were present. Finally, I had to remove the header support for the Shopping lists as the browser caching based off last_updated header was not allowing it to read recent updates due to how we're handling the updated_at property in the database with nested fields. This will have to be looked at in the future to reimplement. I'm unsure how many other routes have a similar issue.
Co-authored-by: Hayden <64056131+hay-kot@users.noreply.github.com>
* migration: add public, tags, and tools
* generate frontend types
* add help icon
* start replacement for tool-tag-category selector
* add help icon utility
* use generator types
* add support for cookbook features
* add UI elements for cookbook features
* fix tests
* fix type error
* update to GUIDs
* fix cookbook id relationships
* update webhook keys
* cleanup naming and attribute orders
* remove old database tables
* fix meal-plan images
* remove dashbaord and events api
* use recipe-id instead of id
* cleanup documentation assets
* cleanup docs for v1 beta-release
* add depends_on for docker-compose
* use docker volumes for examples
* move caddy to frontend container
* feat(backend): ✨ new meal-planner feature
* feat(frontend): ✨ new meal plan feature
* refactor(backend): ♻️ refactor base services classes and add mixins for crud
* feat(frontend): ✨ add UI/API for mealplanner
* feat(backend): ✨ add get_today and get_slice options for mealplanner
* test(backend): ✅ add and update group mealplanner tests
* fix(backend): 🐛 Fix recipe_id column type for PG
Co-authored-by: hay-kot <hay-kot@pm.me>
