Closed daria-github closed 10 months ago
This feels like a reasonable suggestion, and is easy enough to implement. I'll put this into the SDK v8 workstream and add it in.
the conversationId
field has proven to create confusion for developers & end-users, adds non-trivial implementation complexity, and has potential for abuse. the current recommendation is to not use them.
Is your feature request related to a problem?
Currently, the UI is able to send invalid conversation IDs to SDK (due to just requiring a string in order to send to the SDK), which creates an empty conversation. This request is for blocking creating this conversation on SDK side if the conversationId provided is not valid.
PR for reference where this was fixed within an individual app, but doesn't solve the root issue: https://github.com/xmtp-labs/xmtp-inbox-web/pull/92