Add API to resolve configuration object

[muuvmuuv]

Prettier has a function to resolve prettier config before actual formatting, I guess stylelint has something like that under the hood too. Would be nice to have this in the API aswell.

In prettier it looks like this:

    const resolveConfig: typeof ResolveConfig = prettier.resolveConfig;
    return resolveConfig(filePath, { useCache: false }).then((config: any) => confif);

https://prettier.io/docs/en/api.html#prettierresolveconfigfilepath-options

I think stylelints "resolveConfig" is here:

stylelint/lib/printConfig.js

Lines 52 to 54 in 0fb8b6d

	return stylelint
	.getConfigForFile(configSearchPath)
	.then(result => result.config);

[hudochenkov]

What is it use case?

[muuvmuuv]

I'm working on a new beautifier extension for Unibeautify.
Unibeautify has a function called resolveConfig, to retrieve beautifier-specific configuration.
It also provides the possibility to set options for specific languages for multiple beautifiers (prettier, stylelint...), which will be later transformed into readable breautifier config (e.g. stylelint). The function called beautify will then use this config or the config passed to Unibeautify to beautify a file.

[jeddy3]

@muuvmuuv Thanks for writing up your use case.

This is the second request, the other being #3734, to expose some of the internals of stylelint (as part of our API) to the benefit of tool authors. Unless anyone can think of a good reason why not to, I think we should welcome a PR do this (and undertake any necessary refactoring to make it possible) as our internals seem pretty solid and unlikely to change any time soon.

[jeddy3]

Triaging issues...

As no one has raised any objections to this feature, I'm going to label as "help wanted".

@muuvmuuv Feel free to contribute this feature.

[is2ei]

Is this issue still relevant?
It seems #5734 fixed it.