-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing scoped package name for shareable configs #327
Comments
Bump, this is a blocker for me atm. My private organization cannot use the extension system as we need our pkg to be private and scoped. |
@johnnyshankman @jpapini I'm not sure I understand this issue, can you elaborate ? |
@dbale-altoros so right here: you expect the npm package name to start with example is that i want to deploy something like example from npm docs: |
Ok, thanks for the clarification Thanks a lot for posting! |
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
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.
The text was updated successfully, but these errors were encountered: