-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update globby
to v7.1.1
#6639
Update globby
to v7.1.1
#6639
Conversation
Looks like breaking changem try to use |
Sounds like we need to add some tests, then. |
This comment has been minimized.
This comment has been minimized.
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.
see my questions & comment
I have a few more questions:
|
I was trying to make tests the another day, then I got distracted by #6665 . Those options are really confusing me, as I understand,
|
I think part of the confusion is how much globby has changed over quite a few major versions. I think we should try to research and understand this carefully before making any more adjustments. I do think we should also avoid using any options not really needed. I am now really thinking we should consider using the latest rather than trying to deal with the old, unsupported package versions. Unfortunately I don't have much time to look into this right now. |
I tried raising RFC PR #6748 to try globby@10 update for discussion, seems to be mostly working with a few TODO items. I think that nodir setting is not needed in some newer versions of globby, removing it does not cause any failures. I am also thinking that expandDirectories should not be an issue since Prettier only works with files. But I may prove to be mistaken here. |
closing in favor of #6748 |
# Conflicts: # package.json
globby
to v7.1.1dot pattern
and expandDirectories
with globby@7.1.1
@lydell @evilebottnawi @brodybits I reopened this, and add This will not breaking anything, but support |
|
||
expect.addSnapshotSerializer(require("../path-serializer")); | ||
|
||
// TODO: move `multiple-patterns` tests into this one |
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.
Can you explain why we would want to do this in the future?
I would only favor combining tests if they have the exact same output and can help reduce the number of snapshots we have to maintain.
Assuming there would be a good reason to do this, I would really favor adding this comment to tests_integration/__tests__/multiple-patterns.js
as well to avoid losing track of this TODO item.
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.
not all tests are multiple-patterns
, name to patterns
should be more reasonable
If I understand currectly, what do you want is and print is that currect? |
Yes, that’s correct! |
Can you explain to me, what those 4 should be? |
I basically want the same behavior as |
just to clearify not supported extensions, because parser can be override by config. |
For every file we go through, try to resolve the final config to use for that file like we already do. If |
Shouldn't this already be covered by the test suite? If not, I think we should add the missing tests. |
dot pattern
and expandDirectories
with globby@7.1.1
globby
to v7.1.1
I've disabled all the behavior changes, it's only package upgrade now. |
Also don't forget what plugins can add own extensions and it should be tested also (when we implement |
@@ -407,11 +407,13 @@ function eachFilename(context, patterns, callback) { | |||
patterns = patterns.concat(["!**/node_modules/**", "!./node_modules/**"]); | |||
} | |||
patterns = patterns.concat(["!**/.{git,svn,hg}/**", "!./.{git,svn,hg}/**"]); | |||
patterns = patterns.filter(pattern => pattern !== "."); |
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.
Let's add comment here why we do this
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.
done
@fisker please fix conflicts and let's do it for @prettier/core please review |
# Conflicts: # package.json # yarn.lock
Rebased & CI passed. |
What are we going to do with this one? |
@fisker If we can't update globby to latest we need merge this branch |
Closing in favor of #6776 |
withglobby
v7.1.1, we supportdot pattern
andexpandDirectories
now.fixes: #6085docs/
directory)CHANGELOG.unreleased.md
file following the template.✨Try the playground for this PR✨