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
Correct handling of __name__ in firestore indexes (#8862)
* fix(firestore): smart filtering of __name__ fields in index listings
Preserve __name__ fields with DESCENDING order while filtering out
implicit ASCENDING ones to fix deployment conflicts.
- Fixes duplicate index issues (#7629)
- Fixes deployment conflicts (#8859)
- Add comprehensive test coverage
Fixes#7629, #8859
* refactor(firestore): extract index filtering logic to static method
Refactored __name__ field filtering from listIndexes into static method
FirestoreApi.processIndexes() to ensure tests verify production code
rather than duplicating the implementation.
* refactor(firestore): simplify processIndexes filter logic
Simplified the filter expression in processIndexes() to a single boolean
expression as suggested in PR feedback for better readability and
conciseness.
* Update CHANGELOG.md
* Only filters __name__ when order matches order of last non name field and it is the last field
* Super defensive
---------
Co-authored-by: Torben Wetter <[email protected]>
- Fixed issue where `__name__` fields with DESCENDING order were incorrectly filtered from index listings, causing duplicate index issues (#7629) and deployment conflicts (#8859). The fix now preserves `__name__` fields with explicit DESCENDING order while filtering out implicit ASCENDING `__name__` fields.
0 commit comments