Open pinaraf opened 6 years ago
When ticking "also send direct message" :
Chaussette in : "{\"type\":\"message\",\"channel\":\"D4EPF2N22\",\"user\":\"U42KNNKTP\",\"text\":\"test en cochant la case à la con\",\"ts\":\"1528059170.000082\",\"source_team\":\"T03DFHCR8\",\"team\":\"T03DFHCR8\",\"thread_ts\":\"1528057945.000078\",\"reply_broadcast\":true}"
Threads are needed, sadly. Current quick analysis : a thread is created on a channel, with a thread_ts marking the corresponding 'source' message.
=>
Global implementation : extend SlackMessage to have a std::vector answers. These will be the thread answers. Must be fetched later, on demand (?)
In history :
User interface : display the thread inline, like a subtree, with a ± icon to expand/reduce the subtree. Hide by default, highlight when there is some unread content ?
What we don't want : the official slack thread ui.