Use absolute plugin path in configs

[Arcanemagus]

There were some instances where a plugin could be specified by name, and end up not being resolved as a later merge of extended configs would drop the fixed path.

I'm not sure of the best way to write a spec for this, as this will only show up when a module name is used for the plugin, where currently all the specs seem to test relative paths.

This was originally reported by @davidtheclark over here, which provides a nice setup of how to expose this issue.

[davidtheclark]

@Arcanemagus: Thanks so much for looking into this. And good job figuring out that subtle problem.

We already have an outstanding issue to improve integration tests (#569) so I'm happy to just consider tests for this to be part of that effort and merge this.

Thanks again. Good catch.

[davidtheclark]

It was tricky to figure out the way to test that this worked in my Atom editor, but I think I confirmed :)

[ismay]

This hasn't been released yet right? Is there a patch release planned? Because right now this crashes atom when using stylelint-selector-bem-pattern and I'd love to see this merged.

[davidtheclark]

I will release a patch tonight. Sorry.

On Thu, Mar 17, 2016 at 11:23 AM, Ismay notifications@github.com wrote:

This hasn't been released yet right? Is there a patch release planned,
because right now this crashes atom when using
stylelint-selector-bem-pattern.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#913 (comment)

[ismay]

@davidtheclark No problem at all, just wondering :). Thanks!