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

Upgrade broccoli-filter #14

Merged
merged 4 commits into from
Mar 10, 2016

Conversation

nickiaconis
Copy link
Contributor

Provides a solid basis for migrating to broccoli-persistent-filter.

@nickiaconis
Copy link
Contributor Author

@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.

@rwjblue
Copy link
Member

rwjblue commented Mar 10, 2016

Can you rebase (I think latest work for publishing post-babel code caused merge conflicts)?

@nickiaconis nickiaconis force-pushed the filter-upgrade branch 5 times, most recently from 1b21462 to 27069df Compare March 10, 2016 18:26
@nickiaconis
Copy link
Contributor Author

Thanks for the ping. This should be able to merge again.

jonathanKingston added a commit that referenced this pull request Mar 10, 2016
@jonathanKingston jonathanKingston merged commit e09267d into ember-cli:master Mar 10, 2016
@nickiaconis
Copy link
Contributor Author

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

@jonathanKingston
Copy link
Member

Odd must have deleted it, thanks @nickiaconis


this.cli = new CLIEngine(this.eslintOptions);

this.eslintrc = inputTree;
Copy link
Contributor

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.

Copy link
Member

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.

Copy link
Contributor Author

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.

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

Successfully merging this pull request may close these issues.

None yet

4 participants