Feature Support: Enable customization of the contentCollectionCache save location. #793
Closed
justin5267
started this conversation in
Proposal
Replies: 2 comments
-
Hey @justin5267 , here's a suggestion: considering the fact that content collections cache RFC is still open, I think it's best to leave a comment in the PR of the RFC. That's the most appropriate way to leave feedback while a feature is still under the RFC process. No need to open a new discussion unless a feature is already stable. |
Beta Was this translation helpful? Give feedback.
0 replies
-
The content collections cache flag has been removed in v5 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When building static websites, users often directly package all files in the dist folder and upload them to hosting servers. However, currently, the cache files generated by the contentCollectionCache feature are also stored in the dist folder, requiring manual exclusion of relevant folders during the packaging and upload process.
Beta Was this translation helpful? Give feedback.
All reactions