@m4l/testing 1.2.1-beta-docs-autocomplete-async-with-add-mf-sync.0 → 1.2.1-beta-docs-autocomplete-async-with-add-mf-sync.1

package/README.md

@@ -312,7 +312,6 @@ Current shared Vitest helpers in `@m4l/testing/vitest` include:
 - `createM4lAppFormLayoutsModuleOverrides(...)`
 - `createM4lAppCoreModuleMock(...)`
 - `createM4lPackageGclickModuleMock(...)`
-- `createM4lResourceSynchronizationModuleOverrides()`
 - `createM4lPackageGclickRealtimeModuleMock(...)`
 - `createM4lAppGraphicsModuleMock(...)`
   Includes a neutral `useInfinitePaginate()` entry (no rows, `hasMore: false`,
@@ -339,9 +338,8 @@ Current shared Vitest helpers in `@m4l/testing/vitest` include:
 - `createReResizableModuleMock(...)`
 - `createReactLeafletModuleMock(...)`
   Reusable module factories for M4L component consumers plus app and package `test/setup.ts` files so packages, hosts, and MFs can keep thin local adapters instead of repeating the same large `vi.mock(...)` payloads. When a consumer needs untouched real exports too, pass `baseModule` populated from `importOriginal(...)` and let the shared factory override only the test-facing surface.
-  `createM4lAppFormComponentsModuleOverrides(...)` provides a reusable override payload for app/MF `@m4l/components` setups that need the dynamic-MF parameters store plus neutral form container/action placeholders (`FormContainer`, `ActionsContainer`, `ActionFormCancel`, `ActionFormIntro`, `RHFAutocompleteAsync`, and `RHFRadioGroup`) without copying the same local override object across app test setups. The canonical `RHFAutocompleteAsync` mock remains a neutral placeholder; inspect its props for optional `add` configuration without opening a real creation window.
+  `createM4lAppFormComponentsModuleOverrides(...)` provides a reusable override payload for app/MF `@m4l/components` setups that need the dynamic-MF parameters store plus neutral form container/action placeholders (`FormContainer`, `ActionsContainer`, `ActionFormCancel`, `ActionFormIntro`, `RHFAutocompleteAsync`, and `RHFRadioGroup`) without copying the same local override object across app test setups.
   `createM4lAppFormLayoutsModuleOverrides(...)` provides a reusable override payload for app/MF `@m4l/layouts` setups that need neutral paper-form seams (`useDynamicPaperForm`, `useFormAddEdit`) and a configurable `createComponentField(...)` identity baseline without repeating the same setup-local overrides.
-  `createM4lMFActionModuleOverrides()` provides opt-in `completeMFAction` and `isMFActionRequest` spies plus the production `MF_ACTION_REQUEST_PARAM` identity for save-orchestration tests. Request recognition defaults to false and completion is a no-op; individual scenarios can enable recognition or make the observer throw. Compose it through app-component `moduleOverrides` instead of dynamically importing a component implementation from an MF setup, because that dynamic workspace import marks the component package as lazy in Nx's dependency graph. The standard factory continues to preserve real action helpers through `baseModule`; transport and lifecycle behavior have their own component-level tests.
   `createReactHookFormModuleMock(...)` now accepts `useFormContextData` so tests can inject package-local `setValue`, `reset`, `formState`, and related RHF behavior without rebuilding the full `react-hook-form` contract in each file.
   `createLeafletModuleMock(...)` now covers the repeated partial `leaflet` seams that showed up during the `GpsMap` normalization work: configurable `L.control.scale()` and `L.DomEvent.disableClickPropagation()` / `disableScrollPropagation()` behavior, while still preserving real exports through `baseModule` when the consumer needs the untouched runtime surface.
   `createReactLeafletModuleMock(...)` now covers neutral `Circle`, `GeoJSON`, `Polygon`, `Polyline`, `LayerGroup`, `Marker`, `Popup`, and configurable `useMap()` behavior. Use `useMapData` when the test can keep one stable map object for the whole file, or `useMapImplementation` when the test needs `useMap()` to read mutable per-test state such as a late-bound fake map ref. When a test still needs real exports such as `MapContainer`, keep the mock partial by passing `baseModule` from `importOriginal(...)` and override only the shape components or `useMap()` contract that belong to the scenario.
@@ -363,7 +361,6 @@ Current shared Vitest helpers in `@m4l/testing/vitest` include:
   The shared M4L app factories now also cover neutral platform-shell and MF-loading collaborators that repeatedly show up in app tests, including provider passthrough components such as `ModuleDictionaryProvider`, `ModuleSkeletonProvider`, `DomainCountryProvider`, `FormatterProvider`, `ModalProvider`, `PopupsProvider`, `AreasProvider`, `FlagsProvider`, `EnvironmentProvider`, `HostToolsProvider`, `NetworkProvider`, `AuthProvider`, `LocalesProvider`, `ThemeSettingsProvider`, `DeviceTypeProvider`, and `HostThemeProvider`, plus shell primitives such as `SideBar`, `AppBar`, `HelmetPage`, `AreasAdmin`, `LanguagePopover`, `AccountPopover`, `MFNoAuthApp`, `MFLoader`, `createDynamicMFStore(...)`, `createToaster(...)`, `getMFLoaderComponentsDictionary()`, `getLoadingErrorComponentsDictionary()`, and locale/domain hooks such as `useLocales()`, `useDomainCountry()`, and `getLocaleFromNetwork()`.
   The shared base `@m4l/components` layer now also owns reusable view primitives such as `Divider`, `NavLink`, and `WindowBase`, plus focused placeholder helpers such as `createDividerComponentMock(...)`, `createNavLinkComponentMock(...)`, and `createWindowBaseComponentMock(...)` so app tests can stay on top of the setup-owned baseline instead of rebuilding local workspace-library mocks.
   `createM4lPackageGclickModuleMock(...)` remains intentionally specific to the `@m4l/gclick` package and covers map-store, indicator, and GNSS enum behavior that only makes sense when mocking that exact runtime package.
-  `createM4lResourceSynchronizationModuleOverrides()` is an explicit opt-in for MF orchestration suites that need controllable `useResourceInvalidation`, `useResourceMutation`, and `useEntityReferenceAdd` hooks plus the `PERSONS_RESOURCE` and `PROTOCOL_PERSON_REPORT_METHODS_RESOURCE` identities. A lightweight MF setup can use this payload directly without importing the full map/video runtime; a suite that needs other GClick exports can pass it through `moduleOverrides` or combine it with its existing partial mock. The standard package factory keeps these new exports real by default. Each factory invocation owns stable hook results and action functions, so component rerenders do not create artificial subscription changes. The resource contract test imports the real public root while isolating unrelated feature barrels, and compares the two identity constants with production values. Component passthrough contracts reuse the existing real Components preload; the generic autocomplete and MF action helpers remain real unless explicitly overridden.
   The shared app-components baseline now exposes a minimal but stable
   `WINDOW_SIZES.square` contract with both `medium` and `large` entries so app
   tests can open modal windows without each suite rebuilding the same shape