-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
feat: noSync flag for astro check #11482
Conversation
🦋 Changeset detectedLatest commit: e624fe0 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
This PR is blocked because it contains a minor
changeset. A reviewer will merge this at the next release if approved.
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.
Fantastic docs, @Princesseuh 🫡
!preview noSync |
Snapshots have been released for the following packages:
Publish Log
Build Log
|
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.
Usually flags aren't camelCase, so I think this should be named --no-sync
All the flags of astro check are camel cased, it follows |
Changes
There's some niche cases where you want to run
astro check
, but don't want to run the type gen step first. This is especially relevant in complex mono repos where some packages have Astro components, but are not Astro projectsTesting
Tested manually
Docs
withastro/docs#8838