fix: skip legacy typegen by default #12438
Merged
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.
Changes
We now allow content layer collections in
src/content
, and disable the Vite watcher for them unless legacy collections are enabled. However we didn't skip the typegen that also runs via a glob on that folder, meaning that legacy types were being generated. This PR ensures that these are also skipped unless the legacy flag is set.Fixes PLT-2640
Testing
Adds a test case, and updates another of the fixtures.
Docs