Feature Request: dropped_fields in update() response

When calling entity.update(), fields with field-level rls.read restrictions are silently dropped. The response returns modified_count: 1, suggesting success — but the fields are never persisted.

Antworten

Suggestion: Add a dropped_fields array to the update response (e.g. "dropped_fields": ["phone", "birth_year"]) so developers immediately know which fields were filtered out.

Antworten

This would have saved us several hours of debugging. The silent drop + success response is very misleading, especially when using asServiceRole where you'd expect full write access.