It should be exposed as extends option, not baseConfig.extends.

@sindresorhus If desired, all of the baseConfig options can be hoisted by using ESLint's config schema: https://github.com/sindresorhus/grunt-eslint/compare/master...pro-src:hoist_base_config?expand=1
https://github.com/eslint/eslint/blob/master/conf/config-schema.js

And maybe fail hard if an unrecognized option is specified.

@sindresorhus,

I know you have 1k other PRs to like at that are far more interesting but I'm bored so I'm going to bug you anyway. 😜

I'm wondering if you had something else in mind for this PR. As the the issue title is confusing to me. Simply because there is already support for the "extends" option. I get what you mean by it should be exposed as "extends" but it has already been exposed as "extends" by ESLint though nested under the documented baseConfig option. I've taken a guess at what the expectation is for this, made changes, and made some suggestions. So, I don't really know what else to do with it. Also, If you just didn't realize that it was already exposed, feel free to kick this out of limbo and into the trash. I don't mind. 😄

Thanks

Nah, the point is to just make the extends option more discoverable and easier to use by making it top-level and documenting it.

--

I get what you mean by it should be exposed as "extends" but it has already been exposed as "extends" by ESLint though nested under the documented baseConfig option.

Yes, but it's not discoverable.

@kevva Thanks for the review. Did you notice https://github.com/sindresorhus/grunt-eslint/compare/master...pro-src:hoist_base_config?expand=1 ?

It uses the rest operator 👍