You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each time a discussion is modified (addition of members, change of admin, modification of group name, etc.), the discussion transaction chain evolves with updates to the smart contract.
This means that messages sent by users are received in the last address of the smart contract transaction chain.
So a smart contract at index 1 may have 4 messages as inputs, at index 2, 6 messages, etc....
Currently, only the inputs in the last address of the chain are read.
Describe the solution you'd like
The previous addresses must therefore be read to retrieve all the messages.
To avoid performance problems, use the limit property passed to the read method of the MessagesMixin mixin.
If the limit is not reached for the txContentMessagesAddresses list, then the inputs from the previous transaction are retrieved.
Additional context
No response
Epic
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
No response
Describe the solution you'd like
Each time a discussion is modified (addition of members, change of admin, modification of group name, etc.), the discussion transaction chain evolves with updates to the smart contract.
This means that messages sent by users are received in the last address of the smart contract transaction chain.
So a smart contract at index 1 may have 4 messages as inputs, at index 2, 6 messages, etc....
Currently, only the inputs in the last address of the chain are read.
Describe the solution you'd like
The previous addresses must therefore be read to retrieve all the messages.
To avoid performance problems, use the limit property passed to the read method of the MessagesMixin mixin.
If the limit is not reached for the txContentMessagesAddresses list, then the inputs from the previous transaction are retrieved.
Additional context
No response
Epic
No response
The text was updated successfully, but these errors were encountered: