RecordDelete is not being received in a subscription when it is expected

[LiranCohen]

Example Scenario:

1. Bob installs the chat protocol and creates a thread, adding Alice as a participant.
2. Alice creates a subscription to receive events using the delegated grant.
3. Bob writes two chat messages to the thread.
4. Bob deletes one of the chat messages.

Expected: The subscription handler should have received both the chat writes and the delete.
Actual: The subscription received only the writes.

When subscribing using protocol rules, a set of filters are built to match against the indexes created when storing the Delete.
Investigate modifying the filters/indexing to allow for the expected behavior.

[nehaaprasad]

Hello @LiranCohen :)

I think to * Update Subscription Filters: Add the RecordWrite and RecordDelete event types to the filters.

{ "eventType": ["RecordWrite", "RecordDelete"], ... }

• Check Indexing: As with RecordWrite events, make sure RecordDelete events are appropriately indexed.

• Test: Make that the subscription now records both write and delete events by simulating the deletion of messages.