-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message send state #516
Comments
Hey @richardhuaaa , it's the opposite :) It currently returns the group id but it should return the message id (as we already know the group id!) |
Context: #529 |
After https://github.com/xmtp/libxmtp/pull/544/files#diff-3a24c3e76565487a710ac9863ac05160128f4f90892e07849b555a6de43a6e8f, optimistic messages will be inserted into the libxmtp DB and returned to the integrator when listing messages in a conversation, with delivery status UNPUBLISHED.
|
Naomi has a good Q: if the message send fails after 3 retries, do we delete the optimistic message? |
Maybe in addition to UNPUBLISHED and PUBLISHED, we should have a FAILED status |
Maybe add option to filter published/unpublished message |
Getting back the message id from |
Expose optimistic message sends.
Per conversation/request from a partner on April 10, when we do this work, let's make sure
await group.send
returns the group id (it currently returns the message ID)The text was updated successfully, but these errors were encountered: