-
Notifications
You must be signed in to change notification settings - Fork 0
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
backend rewrite #453
base: main
Are you sure you want to change the base?
backend rewrite #453
Conversation
Web should work in one of the previous commits (37bad80) and we can narrow down and debug |
- flatten api file structure - refactor db to use latest drizzle ver - add web fallback for useWarmupBrowser
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good, going to make note of some of the TODOs left in the pr
TODO
Backend
- Add separate tests in
services.test.ts
that test upserts independently of database queries. - Add back the getMenu procedure with router tests
- Flush out the push notification system. We will start off by adding simple push notification tests and error handling.
- Design the system for push notifications to work with pinned items
- [Minor] Add tests for getRestaurantByDate
- Add test for daily and weekly server functions
- Event scraping tests using test HTML file
- Refactor weekly cron job into its own function? (up for debate)
Still need to test front end, will do once my docker decides to work
Changes
Note
Above was already merged.
apiTest()
?
not sure if we should be caching jwt in asyncstorage for web but thats what i did for right nowstopped caching jwt when on web.
Closes #457, Closes #447, Closes #449, Closes #437
demo
2024-05-30.22-22-15.mp4
ui for missing nutrition facts
generated diagram with
db:diagram
script