-
-
Notifications
You must be signed in to change notification settings - Fork 92
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Adjust the way glob roots are calculated
Try to support the "assumed" behavior.
- Loading branch information
Showing
3 changed files
with
27 additions
and
7 deletions.
There are no files selected for viewing
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
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
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
d1a7fa7
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.
@Jason3S Can you explain this change a bit more? I suddenly have a build failing with lots of my ignorePaths no longer working. E.g. I have
"html/**"
as one of my ignorePaths and suddenly files underhtml/
are being scanned when before they would be ignoredd1a7fa7
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.
@Jason3S Seems like it was #913 with the change to the globRoot. Can you please add a "Breaking Change" section to the changelog the gives details of this. Thanks
d1a7fa7
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.
@timwsuqld Sorry about breaking your build.
I would like to understand how this change impacted you. Do you happen to have a sample repo I can look at?
Specifically where is the configuration file (cspell.json) file located relative to the files being checked.
d1a7fa7
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.
@Jason3S unfortunately no sample repo that's public. But simply we had a config located at
tests/spellcheck-settings.json
similar to this:We call
cspell
in CI with the commandcspell --config=tests/spellcheck-settings.json $(git ls-files)
(after installnpm install -g cspell
, which I later realised was my bad for not locking it to a specific version)The simple fix was adding a
globRoot
It was my bad for not locking the cspell version. Having a
BREAKING
changes section to a changelog would also help, as it would let me quickly search for what breaking changes the newer release had, and ideally would point me to documentation explaining what I needed to change to have things working correctly.d1a7fa7
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.
I agree, a
BREAKING
section would help. The comments were in the pull requests, but did not make it into the CHANGELOG.