-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Upgrade broccoli-filter #14
Upgrade broccoli-filter #14
Conversation
ea8dee3
to
65ff52a
Compare
@jonathanKingston I've reworked the tests so we can write different assertions for different filter input. I've also added that test I mentioned in #6 for using the relative config file. |
Can you rebase (I think latest work for publishing post-babel code caused merge conflicts)? |
1b21462
to
27069df
Compare
27069df
to
d1e1e30
Compare
Thanks for the ping. This should be able to merge again. |
Upgrade broccoli-filter
Fantastic! Btw, I noticed the TravisCI badge in the readme, but it seems Travis isn't turned on for this repo. You can turn it on if you'd like. Everything's currently passing: https://travis-ci.org/nickiaconis/broccoli-eslinter/builds/115141736 |
Odd must have deleted it, thanks @nickiaconis |
|
||
this.cli = new CLIEngine(this.eslintOptions); | ||
|
||
this.eslintrc = inputTree; |
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.
This seems to assume that inputTree
is the srcDir
string. Isn't inputTree
an object? This breaks the paths in processString
later on when we concatenate it to relativePath
.
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.
@nickiaconis can this be addressed in #21? Pretty sure @teddyzeenny is right.
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.
Good point. All the tests provide a string as the input node, so I overlooked the possibility that this could be a tree instance. Any ideas how to resolve this from a tree? My first thought is to recursively resolve the _inputNodes
objects until we get a string, but this doesn't account for merge trees.
Provides a solid basis for migrating to broccoli-persistent-filter.