-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Making sure each plugin indicates its default group and feature when … #16728
base: main
Are you sure you want to change the base?
Conversation
…applicable. Updating `plugin_group!`` macro to include the plugin's meta information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat idea, and I like the notes.
Two things:
- this macro really needs comments to explain how / why it works. I'm very surprised that we can modify docs for the plugin itself!
- the newly added lines should be below the manually added docs
That makes two of us, I wasn't expecting it. Maybe you can ask the original developers to add those, I just modified it to include the
I'll change that. You want to me remove the macro changes until someone can come along and explain/comment why it works? |
Leave the macro changes for now: I think they're an improvement :) |
@seivan Gentle reminder about this PR :) It's not far off merging now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the added doc on plugins should be the first line
the first line of docs is used by the html doc as a summary and presented alone in some context
Sorry, was away. I’ll get on the changes requested tomorrow. 👌🏼 |
Yep @alice-i-cecile said as much, I will change it. |
Objective
plugin_group!
macro to include the plugin's meta information.Solution
cfg
flags when usingplugin_group!
Testing