https://sonarly.com/issue/41644?type=bug
Editing a Person record can crash the People page when an in-memory query filter references a field key that no longer exists in current metadata.
Fix: I implemented a defensive fix in the record filter matcher to prevent stale filter keys from crashing optimistic updates:
- In `isRecordMatchingFilter`, when a filter key cannot be resolved to current object metadata, it now returns `false` (record does not match) instead of throwing.
- This keeps optimistic cache update flows resilient when metadata changed (e.g., custom field removed/renamed) but cached query filters still reference the old key.
- Added unit tests in `isRecordMatchingFilter.test.ts` to lock behavior:
- unknown filter field returns `false`
- implicit-and with one unknown field returns `false`
Authored by Sonarly by autonomous analysis (run 47504).
sonarly-bot
669f44848b