Thomas Camlong
d0709a684c
The in-memory request handler cache introduced in #6075 keyed entries by JSON.stringify(input) in a Map shared across all handlers. Any two handlers querying the same integration with equal options (e.g. {}) collided and read each other's data — with the mock integration serving every widget kind, all demo widgets received whichever handler's data was cached first (beszel getting health-monitoring payloads, etc.). Cache keys are now namespaced per handler definition. Also disable the query-cache persister after the first FORBIDDEN response so demo mode doesn't retry a mutation that is always rejected.
Create T3 App
This is a T3 Stack project bootstrapped with create-t3-app.
What's next? How do I make an app with this?
We try to keep this project as simple as possible, so you can start with just the scaffolding we set up for you, and add additional things later when they become necessary.
If you are not familiar with the different technologies used in this project, please refer to the respective docs. If you still are in the wind, please join our Discord and ask for help.
Learn More
To learn more about the T3 Stack, take a look at the following resources:
- Documentation
- Learn the T3 Stack — Check out these awesome tutorials
You can check out the create-t3-app GitHub repository — your feedback and contributions are welcome!
How do I deploy this?
Follow our deployment guides for Vercel and Docker for more information.