Skip to content
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

Change scoped plugins name handling #4011

Closed
hueniverse opened this issue Dec 27, 2019 · 0 comments
Closed

Change scoped plugins name handling #4011

hueniverse opened this issue Dec 27, 2019 · 0 comments
Assignees
Labels
breaking changes Change that can breaking existing code
Milestone

Comments

@hueniverse
Copy link
Contributor

hueniverse commented Dec 27, 2019

No changes to plugin registrations and dependencies (the name provided is matched as-is). When using server.expose() in a scoped plugin, the name used under server.plugins defaults to no scope (breaking change). This can be changed to keep the scope with a new third argument { scope: true } option, or rewrite the scope to 'scope__name' with { scope: 'underscore' }.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking changes Change that can breaking existing code
Projects
None yet
Development

No branches or pull requests

1 participant