Widget implementation advanced topics
In starting to think in-depth about Work Item widgets relating to #353624 (closed), we started to get into some future-looking questions that I wanted to have a place to discuss in further depth so that we don't lose track of them (while staying focused on an MVC approach for Tasks)
We can open discussion threads here.
🤖
Auto-Summary Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:
. For example, the following are all valid points:
#### POINT: This is a point
* point: This is a point
+ Point: This is a point
- pOINT: This is a point
point: This is a **point**
Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:
. For example, the following are all valid topics:
# Topic: Inline discussion topic 1
## TOPIC: **{+A Green, bolded topic+}**
### tOpIc: Another topic
Quick Actions
Action Description /discuss sub-topic TITLE
Create an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINK
Link an issuable as a child of this discussion
Last updated by this job
- TOPIC Do we need some mechanism for widgets / widget updates to communicate with other parts of the application or each other? #354022 (comment 858955612)
- TOPIC How do we determine when updating a widget should be included in the WorkItemCreate or WorkItemUpdate mutation vs. when it needs its own mutation? #354022 (comment 858957332)
Discoto Settings
---
summary:
max_items: -1
sort_by: created
sort_direction: ascending
See the settings schema for details.