-
Notifications
You must be signed in to change notification settings - Fork 41
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 configuration via system console #92
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.
Approving with one nit suggestion.
Co-authored-by: Jason Frerich <[email protected]>
@AayushChaudhary0001 Would you be open to reviewing this PR? |
Note that there is a similar PR being finished up that implements a custom admin component for this Brightscout#15. I think this PR can/should be closed in favor of the custom component implementation. Are you okay with this @jwilander? |
Yes, let's close in favour of that. |
Opening this PR due to comments #108 (comment) and #108 (comment). |
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.
@Kshitij-Katiyar While testing this PR, it was found that this was not working for MM cloud server. Any new user added to a team was not getting any welcome message nor any action button. Please verify it once.
Closing the PR because of the PR #126 |
Summary
I wanted to make this plugin configurable via the System Console, since doing it with mmctl was causing me issues and I wanted to update it often. But, because the plugin manifest settings schema only offers strings and other primitive types as options, I needed the configuration for
WelcomeMessages
to support being either a string or a JSON array. Hence, the customUnmarshalJSON
forConfiguration
.It's not an ideal solution but it works decently well. The other method I considered taking was using the
custom
settings schema type but then I'd have to re-implement the text field component and add a web app component to this plugin, which I didn't want to do. Thoughts?