For those of you not using earlier Comments v1, one of my favorite use case is to link the Thread ID to a dynamic Retool value like {{ table1.selectedRow.id }}. Instead of copying the link or ID, switching the to your other favorite chat app and pasting it there, starting a thread right on Retool is so much faster!
With updated APIs and Event Handlers, you can send and handle submission programmatically. One of my favorite use case is to set Submit Handler to a Retool email query, and send a email notification for everyone on the thread for every new message:
How do I start using this
Comment Thread is available for cloud and on-prem 3.80 and above. You should be able to find it in the component library.
For those of you using the Comment v1 component, you could one-click upgrade to the new Comment Thread, and all of your existing conversations will still be available.
The mentions is very much in consideration! But no specific timeline on that yet. In the mean time, could some combination of submit handler + email work for yall? Happy to chat more on depth about how that could work!
Very appreciate these points about making it more fully-featured! I'm also interested in how you might use this within retool app, how it'd work with other retool components as well.
Happy to do this live as well and talk through ideas.
Overall let's say there is an Incident and we wanna track progress/notes, once Incident is closed we want the comments to be read-only and completely hide input (though we could potentially do this with CSS).
Tried to use a timestamp casted to string, comment gets posted - it says - but it doesn't show up in the thread. It seems a bug to me: ThreadID must somehow be truncated before saving -> no way to fetch using the "raw" id. If cannot be fixed (e.g. fixed schema), the limitation should be made public i.e. max length - or better, an error
