-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Global components #515
Comments
Why not register global components in |
Did that before, thought it might be handy to do that based on file structure rather than config. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
Allow the user to register components globally, without digging in configs.
What problem does this feature solve?
When using components like
<warning-message>Heads up!</warning-message>
oftenly throughout Markdown, it becomes repetetive to add a script block that imports and registers the component.What does the proposed API look like?
Maybe also configurable:
How should this be implemented in your opinion?
Probably as core functionality, possibly as a plugin if desired.
Are you willing to work on this yourself?
Yes.
The text was updated successfully, but these errors were encountered: