-
Notifications
You must be signed in to change notification settings - Fork 108
Make an example of using the Custom Status plugin API methods #146
Copy link
Copy link
Open
Labels
Difficulty/1:EasyEasy ticketEasy ticketGood First IssueSuitable for first-time contributorsSuitable for first-time contributorsHacktoberfestHelp WantedCommunity help wantedCommunity help wantedTech/GoType/EnhancementNew feature or improvement of existing featureNew feature or improvement of existing featureUp For GrabsReady for help from the community. Removed when someone volunteersReady for help from the community. Removed when someone volunteers
Metadata
Metadata
Assignees
Labels
Difficulty/1:EasyEasy ticketEasy ticketGood First IssueSuitable for first-time contributorsSuitable for first-time contributorsHacktoberfestHelp WantedCommunity help wantedCommunity help wantedTech/GoType/EnhancementNew feature or improvement of existing featureNew feature or improvement of existing featureUp For GrabsReady for help from the community. Removed when someone volunteersReady for help from the community. Removed when someone volunteers
With the additions from mattermost/mattermost#17435 (comment), plugins can now access the APIs around managing a user's custom status. This makes it so plugins can:
The task here is to create slash commands to make use of these newly added methods:
/demo custom_status get/demo custom_status update (...value)/demo custom_status deleteEach command should reflect the current user's custom status state.
You will need to deploy the commit from the PR mattermost/mattermost#17435 to have access to the plugin API methods. To checkout this code:
cd mattermost-server- wherever you have this on your filesystemhub pr checkout 17435