-
Notifications
You must be signed in to change notification settings - Fork 196
Open
Labels
Description
According to the doc, shareable configs can only be named with the solhint-config- prefix.
These lines confirms this rule:
solhint/lib/config/config-file.js
Lines 68 to 81 in 3443eee
| const configGetter = path => { | |
| let extensionPath = null | |
| if (path.startsWith('solhint:')) { | |
| extensionPath = getSolhintCoreConfigPath(path) | |
| } else { | |
| // Load packages with rules | |
| extensionPath = `solhint-config-${path}` | |
| } | |
| const extensionConfig = require(extensionPath) | |
| return extensionConfig | |
| } |
But I think we should allow users to name their packages with a scope like ESLint (doc).
For example:
@scope/solhint-config or @scope/solhint-config-myconfig.
This would support packages that are hosted on private repos like GitHub or Package Cloud.
Reactions are currently unavailable