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
Add props to plugin manifest #10124
Add props to plugin manifest #10124
Conversation
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.
We use Props elsewhere for similar purpose, so I think the naming is consistent.
While I generally support this PR, I am 1/5 that a more flexible alternative would be to store the full manifest text "as is" in addition to unmarshaling/normalizing the known fields out of it. This way plugin developers can include custom data anywhere in the manifest, and access it later.
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.
LGTM 👍
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.
As per above
Thanks! Ready to merge |
@levb Lets keep this idea deferred until we have a use case that we can support with |
Summary
This PR allows plugin to include arbitrary data in the manifest. This data can be used by other plugin. My use case is the update plugin (https://github.com/hanzei/plugin-update/).
See https://github.com/hanzei/mattermost-plugin-sample/blob/master/plugin.json for an example how this looks like.
1/5 on the naming.