IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:
Customer cannot realize which documents are deleted on a gRPC call to the Firestore.Listen gRPC endpoint (FireStore server).

How this might work:
Per Customer it would be greatly helpful to have a delete support upon resume with the Listen gRPC call or  for a real CDC implementation (For example, Mongo change streams).

If applicable, reasons why alternative solutions are not sufficient:
Customer does not have access to alter data for the proposed workaround.
Customer would like to use the firestore.googleapis.com gRPC calls/interfaces.

Other information (workarounds you have tried, documentation consulted, etc):
User could consider doing logical deletion with "is_deleted" or "deleted_at" fields, and have a seperate query listen to the "is_deleted == true"/"deleted_at != null", if this is a way they would like to try out.