Skip to content

Allowing scoped package name for shareable configs #327

@jpapini

Description

@jpapini

According to the doc, shareable configs can only be named with the solhint-config- prefix.
These lines confirms this rule:

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions