Closed nuno-vieira closed 3 weeks ago
1 Message | |
---|---|
:book: | Skipping Danger since the Pull Request is classed as Draft /Work In Progress |
Generated by :no_entry_sign: Danger
title |
develop |
branch |
diff |
status |
---|---|---|---|---|
StreamChat | 6.92 MB | 6.92 MB | +1 KB | 🟢 |
StreamChatUI | 4.95 MB | 4.95 MB | 0 KB | 🟢 |
Issues
166 New issues
0 Accepted issues
Measures
0 Security Hotspots
83.4% Coverage on New Code
0.1% Duplication on New Code
@martinmitrevski Closing it then, we can re-open if we revive this
🔗 Issue Links
None
🎯 Goal
PoC to test how creating live ephemeral messages would work.
How to use
The
ComposerVC
example should be simple to understand on how to use it. There 3 newChannelController
methods:createEphemeralMessage()
: This one creates the ephemeral message ready to be updated. You need to store the messageId somewhere.updateEphemeralMessage()
: This one should be used to live update the content of the message.publishEphemeralMessage()
: This one should be used to publish the message to the server.There is also an alternative approach here that uses an
EphemeralMessageUpdater
object, but I think for now this one is simple enough. In the future we should refine and decide the final API. We could even opt for creating a new controller or object, that handles the state of the ephemeral message, but will discuss this internally.Update
Tried a new, simpler version, which contains only 2 methods, and is easier to use:
channelController.ephemeralMessageEditor.updateMessage(text:)
channelController.ephemeralMessageEditor.publish()