We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
allows plugin names to be valid JS identifiers
For example: @seneca/gateway-auth should be findable via: @seneca/gateway-auth gateway-auth GatewayAuth
@seneca/gateway-auth
gateway-auth
GatewayAuth
and with tag:
@seneca/gateway-auth$foo gateway-auth$foo GatewayAuth$foo
@seneca/gateway-auth$foo
gateway-auth$foo
GatewayAuth$foo
is this a convention? warning if plugin name not standard?
The text was updated successfully, but these errors were encountered:
rjrodger
No branches or pull requests
allows plugin names to be valid JS identifiers
For example: @seneca/gateway-auth should be findable via:
@seneca/gateway-auth
gateway-auth
GatewayAuth
and with tag:
@seneca/gateway-auth$foo
gateway-auth$foo
GatewayAuth$foo
is this a convention? warning if plugin name not standard?
The text was updated successfully, but these errors were encountered: