Closed andrelas1 closed 2 years ago
This was released in 0.6.2
. Thank you so much @andrelas1 !
This appears to break my ESLint visual studio code extension, which is run from a different location than the relative path within the rule
Could you share a way to reproduce that @coler-j ?
Is your feature request related to a problem? Please describe. The
no-uninstalled-addons
rule does not provide a custom path for the package.json. It should provide that in the rule configuration.Describe the solution you'd like The solution would be to add a custom schema to this rule, where the location of the package.json can be specified in there.
Describe alternatives you've considered That would be the best and most explicit option.
Additional context No additional context.