-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix glob option of .yeti.json #778
Conversation
It is now not use Globstar if you are also using the Globstar, because it would match up to file under `node_modules` directory.
@okuryu Looks like Travis had an issue with this PR, do you see the same test failure on your side? |
@triptych No. I think that doesn't matter my change and this Travis CI error. |
@okuryu Thanks for submitting this patch and sorry for the delay in our response. It looks like the proposed change would work inside the root level directory. However, the current .yeti.json file also uses the globstar pattern to limit tests to the current component. Perhaps we can create another .yeti.json inside of src to workaround this problem? The one inside of src can be like the original except the basedir would be .. instead of . |
@reid Thank you for your response!
I assumed
How about enhance options of
|
@okuryu Okay. I've opened yui/yeti#57 to get that feature into Yeti. The use of two configuration files can be used to mitigate the problem in the meantime. |
@reid Thanks for file a ticket! |
This option is intended to exclude globbed directories. Fix yui#57. See also yui/yui3#778.
Yeah, this is no longer needed for me. Closing makes sense to me. |
It is now not use Globstar if you are also using the Globstar, because it would match up to file under
node_modules
directory.So I would like to push this against
dev-master
branch because this doesn't affect the source code and test code./cc @reid