fix: unitId is now set for sensitive cms with default homeUnit

[bridgesr]

No description provided.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[HasanCPS]

Duplicated registeringUnitId fallback — extract to a shared hook

The exact same useMemo block now appears in two components. If the fallback priority ever changes (or a third page needs it), two places need updating (components/case-registration/first-hearing-page/index.tsx).

// Current (duplicated in both files)
const registeringUnitId = useMemo(() => {
  return (
    state.formData.registeringUnitText?.id ??
    state.apiData.areasAndRegisteringUnits?.homeUnit?.id ??
    null
  );
}, [
  state.formData.registeringUnitText,
  state.apiData.areasAndRegisteringUnits?.homeUnit?.id,
]);

// Suggested: src/ui-spa/src/common/hooks/useRegisteringUnitId.ts
import { useContext, useMemo } from "react";
import { CaseRegistrationFormContext } from "../providers/CaseRegistrationProvider";

export const useRegisteringUnitId = () => {
  const { state } = useContext(CaseRegistrationFormContext);
  return useMemo(
    () =>
      state.formData.registeringUnitText?.id ??
      state.apiData.areasAndRegisteringUnits?.homeUnit?.id ??
      null,
    [
      state.formData.registeringUnitText?.id,
      state.apiData.areasAndRegisteringUnits?.homeUnit?.id,
    ],
  );
};

[HasanCPS]

No unit/integration tests for the new fallback behaviour

Four components gain new branching logic (sensitive vs. non-sensitive) and a new useEffect with conditional dispatch. A regression here would silently re-break the defect. At minimum, add a test for:

• CaseRegistrationPage: after RESET_FORM_DATA, the home-unit effect re-applies areaOrDivisionText and registeringUnitText when the area is sensitive.
• CaseAssigneePage / FirstHearingPage: registeringUnitId resolves to homeUnit.id when registeringUnitText.id is null.

[renjithabby]

i think the changes in the case-assignee page , first hearing page , and this page can be removed if you add default registering unit just like default case area in caseRegistrationPage if is a sensitiveCase. CaseRegistrationPage line 185

if (!state.formData.areaOrDivisionText.id && areasData?.homeUnit) {
dispatch({
type: "SET_FIELDS",
payload: {
data: {
areaOrDivisionText: {
id: areasData.homeUnit.areaId,
description: areasData.homeUnit.areaDescription,
},

// include the registering unit here if it is sensitive case
},
},
});