-
Notifications
You must be signed in to change notification settings - Fork 170
Use custom post type to display TODO list #86
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/GoTech/ReactJSType/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/GoTech/ReactJSType/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
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently, the TODO list that gets posted daily or by
/github todolooks something like this:This works ok but it's hard to read, is only minimally functional and I think we can add something that does way better. Plugins have a cool feature that lets you use custom post types to render your own React components in place of the regular post components. Leveraging this we can:
I started working on this in the
unreads-v2branch with the following commit 54e8ecf but stopped for two reasons: 1) I ran out of time and 2) plugins could not use custom post types for ephemeral messages (which the/github todocommand returns). As of the next Mattermost version 5.12 coming out soon, 2) is possible thanks to mattermost/mattermost-webapp#2759. Unfortunately, 1) is still the case as I'm still a bit too busy to work on it.If someone is interested in picking up where I left off I think this would be a really great feature that would take the GitHub plugin to the next level. It'll require a bit of everything from server side, front end, UX design and merging master into my branch.
Here's what it was looking like when I stopped: