https://sonarly.com/issue/34403?type=bug
When a workspace's data model changes (schema version mismatch), the metadata store refreshes and removes deleted objects. Components like ViewBarPageTitle re-render with stale URL params before the redirect to /not-found executes, causing an unhandled throw.
Fix: Replaced unsafe `useParams()` + `useObjectNameSingularFromPlural()` pattern with `useRecordIndexContextOrThrow()` in two ViewBar components that crash during metadata refresh:
1. **`ViewBarPageTitle.tsx`**: Removed `useParams()` and `useObjectNameSingularFromPlural` imports. Now gets `objectNameSingular` from the RecordIndex context (which is only rendered when the object metadata is valid).
2. **`useSortsFromQueryParams.ts`**: Same pattern — removed `useParams()` and `useObjectNameSingularFromPlural`, replaced with `useRecordIndexContextOrThrow()` to get the validated `objectNameSingular`.
This follows the exact same fix pattern already applied in commit `9b1e6d5a9d` to `QueryParamsFiltersEffect` and `useFiltersFromQueryParams`. These components are only ever rendered inside `RecordIndexContainerGater`, which guards rendering with a check that `objectMetadataItem` is defined — so the RecordIndex context is always populated when these components mount.
Sonarly Claude Code
99011a2b49