Add the resolvePath option

[fatfisz]

Adds the getRealPath option, thus solving the #165 issue.

I used the getRealPath name, but maybe just transform would be good? But then getRealPath is exposed in the module... I just have a tiny doubt about the name. Maybe it would be good to instead expose transform and use that instead of getRealPath consistently.

I'm marking this as WIP because it depends on the changes from #194.

[codecov]

Codecov Report

Merging #195 into master will not change coverage.
The diff coverage is 100%.

Impacted Files	Coverage Δ
src/utils.js	100% <100%> (ø)	⬆️
src/getRealPath.js	100% <100%> (ø)
src/normalizeOptions.js	100% <100%> (ø)	⬆️
src/index.js	100% <100%> (ø)	⬆️
src/resolvePath.js

[tleunen]

One issue I see is that a user who decide to defines resolvePath for a very specific use case has no way to call the default resolver (from the plugin) for all other paths.

[fatfisz]

It's possible to import it from the plugin though; the default resolver is exported and there's a test for supplying it through the resolvePath option. Or is it about something else? 07.07.2017 1:04 AM "Tommy" <notifications@github.com> napisał(a): One issue I see is that a user who decide to defines resolvePath for a very specific use case has no way to call the default resolver (from the plugin) for all other paths. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#195 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFuevkJfM7OjQPbWCRBhBuOtm5b7qIuoks5sLWfzgaJpZM4N2YiI> .

[tleunen]

Oh yes I see, indeed, the user can import the default function and use it explicitely as a fallback.