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.

Sign up for GitHub

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

Jump to bottom

Consistent plugin namespaces #2982

Closed
RunDevelopment opened this issue Jul 4, 2021 · 1 comment
Closed

Consistent plugin namespaces #2982

RunDevelopment opened this issue Jul 4, 2021 · 1 comment
Labels
plugins
Milestone
2.0

Comments

@RunDevelopment
Copy link
Member

Right now, the namespaces plugins create in Prism.plugins aren't consistent. Some use lower camel case for the name, some use upper camel case, and some use all lower case. Others don't have a namespace at all and just register a few hooks.

The goal of this issue is to have consistent namespaces for all plugins.

We also have to answer the question as to whether each plugin must have a namespace.
@RunDevelopment RunDevelopment added this to the 2.0 milestone Jul 4, 2021
@RunDevelopment
Copy link
Member Author

In v2, all plugins now use lower camel case. The namespace name is derived from the plugin's component id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
plugins
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
1 participant
@RunDevelopment