feat: Cache api schema for build #9126
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
lforst
approved these changes
Feb 13, 2024
cleptric
approved these changes
Feb 13, 2024
|
You may wanna use react's |
|
@lforst too fancy, merging now |
Actually the exported method that calls this function ( |
|
The build logs mention something about something not being able to be cached bc the data is >2MB. Maybe it's not caching it because of that - which would be weird because especially in cases where the data is big, I want it cached. 🤔 |
mjq-sentry
pushed a commit
that referenced
this pull request
Feb 15, 2024
This reverts commit 680c7c4.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Vercel build was error because we make a request for every page we generate, this add a simple cache.