Ignore ziggy.js in Prettier #68
Merged
Conversation
This file contains hidden or 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
tnylea
approved these changes
Mar 3, 2025
D4ve-R
pushed a commit
to D4ve-R/vue-starter-kit
that referenced
this pull request
Mar 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The included GitHub test workflow runs
php artisan ziggy:generatewhich creates theresources/js/ziggy.jsfile. This generated file would have its formatting changed when running Prettier with the included config.This means that if the user adds a formatting check as part of their test workflow (e.g.
prettier --check) it will fail.As the file is auto-generated there should not be any issues ignoring it when manually running Prettier outside of the test workflow.