https://sonarly.com/issue/7596?type=bug
The `NavigateToPreviousRecordSingleRecordCommand` and `NavigateToNextRecordSingleRecordCommand` components throw "Selected record ID is required" when rendered on an index page (or during a show-to-index page transition) because the server-driven command menu path lacks the `availableOn` view-type guard present in the legacy path.
Fix: Created a new `useSelectedRecordIdOrNull` hook that returns `null` instead of throwing when no record is selected. Updated `NavigateToPreviousRecordSingleRecordCommand` and `NavigateToNextRecordSingleRecordCommand` to use this non-throwing variant. Both components now return `null` (render nothing) when there's no selected record, preventing the "Selected record ID is required" error during page transitions.
The root cause is that the server-driven command menu path (`IS_COMMAND_MENU_ITEM_ENABLED` feature flag) can render these components during show-to-index page navigation transitions before the context store atoms are fully updated via `useEffect`. The legacy path had synchronous `availableOn: [SHOW_PAGE]` filtering that prevented this. Rather than restructuring the server-driven path's filtering architecture, this fix makes the two affected components resilient to the transient state.
**Files changed:**
1. `useSelectedRecordIdOrNull.tsx` (new) — Non-throwing variant of `useSelectedRecordIdOrThrow`, returns `null` when no record is selected
2. `NavigateToPreviousRecordSingleRecordCommand.tsx` — Uses `useSelectedRecordIdOrNull`, returns `null` when no record
3. `NavigateToNextRecordSingleRecordCommand.tsx` — Same change as above
Sonarly Claude Code
89516f06bb