-
-
Notifications
You must be signed in to change notification settings - Fork 293
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
Add settings
and parser
options
#142
Conversation
Weird thing though, when I use this to set the generated config:
settings that the import plugin receives:
Does eslint not properly merge the settings? |
Meep? |
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 also add it to the readme?
@@ -73,6 +75,12 @@ test('buildConfig: rules', t => { | |||
t.deepEqual(config.rules, rules); | |||
}); | |||
|
|||
test('buildConfig: settings', t => { | |||
const settings = {'import/resolver': 'webpack'}; | |||
const config = manager.buildConfig({settings: settings}); |
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.
const config = manager.buildConfig({settings});
// @jfmengels in case you have any idea what could cause this. |
Sorry, don't have a clue 😕 |
Ok, figured it out. It's because we pass these option to the ESLint Node.js API, not as normal config (since it's generated). The ESLint Node.js API doesn't yet have a |
@sindresorhus it turns out you're supposed to pass the config via |
@wmertens Ah ok. Makes sense. Can you update to use |
settings
option
No pressure on this, but I plan on doing a new release in a few days, so this needs to be updated if you want it included ;) |
Noted, will try ☺ On Mon, Oct 3, 2016, 9:27 AM Sindre Sorhus notifications@github.com wrote:
|
Last chance. Tomorrow is release day ;) |
@sindresorhus Alright, this should do the trick… |
Awesome. Glad we could land this before the release. Thank you @wmertens :) |
Closes #138.