Demand: Kapa "Exception Handling & Streaming" cluster - 20 conversations / 11 users (largest cluster). PRs #571/#572/#573 cover the server-side exception half; this issue covers the rest.
Problem: No guidance on handling errors on the client, avoiding leaking sensitive data in error messages, or distinguishing timeout vs app errors. Streaming docs are generic - no filtered-query or real-time examples.
Scope:
04-exceptions.md: "Handling errors on the client" + "Don't leak sensitive data" best-practice section; pointer to input validation.
15-streams.md: worked example streaming a filtered DB query (e.g. live updates for where id = …); a real-time location/feed example.
Demand: Kapa "Exception Handling & Streaming" cluster - 20 conversations / 11 users (largest cluster). PRs #571/#572/#573 cover the server-side exception half; this issue covers the rest.
Problem: No guidance on handling errors on the client, avoiding leaking sensitive data in error messages, or distinguishing timeout vs app errors. Streaming docs are generic - no filtered-query or real-time examples.
Scope:
04-exceptions.md: "Handling errors on the client" + "Don't leak sensitive data" best-practice section; pointer to input validation.
15-streams.md: worked example streaming a filtered DB query (e.g. live updates for where id = …); a real-time location/feed example.