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
I have two collections, chats and messages, with two way relation attributes between them.
One Chat can contain many messages, one message can contain one chat.
When subscribing to a chat document no event gets send to the client when a message with a relation to that chat is created.
The relation gets updated inside the chat document.
I don't know if this is expected behaiviour, i cloud now find anything related to that inside docs.
👍 Expected behavior
Fire a realtime update event when a message gets added to the chat document via relation
👎 Actual Behavior
Realtime event only gets triggerd when message is created without a relation to a chat document and then chat is updated to establish the relation with the message
🎲 Appwrite version
Version 1.3.x
💻 Operating system
MacOS
🧱 Your Environment
SvelteKit
👀 Have you spent some time to check if this issue has been raised before?
👟 Reproduction steps
I have two collections, chats and messages, with two way relation attributes between them.
One Chat can contain many messages, one message can contain one chat.
When subscribing to a chat document no event gets send to the client when a message with a relation to that chat is created.
The relation gets updated inside the chat document.
I don't know if this is expected behaiviour, i cloud now find anything related to that inside docs.
👍 Expected behavior
Fire a realtime update event when a message gets added to the chat document via relation
👎 Actual Behavior
Realtime event only gets triggerd when message is created without a relation to a chat document and then chat is updated to establish the relation with the message
🎲 Appwrite version
Version 1.3.x
💻 Operating system
MacOS
🧱 Your Environment
SvelteKit
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: