Skip to content
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

./lint is too slow and can't check only a subdirectory #5598

Closed
smfr opened this issue Apr 18, 2017 · 2 comments
Closed

./lint is too slow and can't check only a subdirectory #5598

smfr opened this issue Apr 18, 2017 · 2 comments
Labels

Comments

@smfr
Copy link
Contributor

smfr commented Apr 18, 2017

./lint seems to trawl the entire repo looking for issues. It could be much smarter and only look at files for which I have local changes, or stashed changes.

I would also like it to be able to only check a subdirectory, like:

./lint css

@annevk annevk added the infra label Apr 18, 2017
@gsnedders
Copy link
Member

gsnedders commented Apr 18, 2017

If you're on an up-to-date (or a sufficiently old!) branch, which #5597 implies you aren't, you should be able to pass files (but not directories) to lint, so find css -type f -print0 | xargs -0 ./lint. There's w3c/wpt-tools#184 for adding some recursive option (or maybe that should just be the default), and there's been occasional discussions about making it faster in various ways but most of that requires a fair amount of refactoring hence nothing has happened.

@smfr smfr closed this as completed Apr 19, 2017
@smfr
Copy link
Contributor Author

smfr commented Apr 19, 2017

Dup of #184

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants