@equinor/fusion-framework-module-context 9.0.0-next.0 → 9.0.0

package/CHANGELOG.md

@@ -1,81 +1,58 @@
 # Change Log
 
-## 9.0.0-next.0
+## 9.0.0
 
 ### Major Changes
 
-- 2836e0b: Add `./mock` and `./mock/fixtures` subpaths for seeding context in tests without a real context API.
-
+- f663b46: Add `./mock` and `./mock/fixtures` subpaths for seeding context in tests without a real context API.
+  
   **BREAKING CHANGE:** `ContextModuleConfigurator` now extends `BaseConfigBuilder` (aligning with `module-event`, `module-http`, `module-msal`, and `module-service-discovery`). Its public `createConfig` method now returns `Observable<ContextModuleConfig>` instead of `Promise<ContextModuleConfig>`. Code calling `await configurator.createConfig(init)` directly should switch to `createConfigAsync`, which keeps the previous Promise-based behavior:
-
+  
   ```typescript
   // Before
   const config = await configurator.createConfig(init);
   // After
   const config = await configurator.createConfigAsync(init);
   ```
-
+  
   No other public export changes as part of this refactor.
-
+  
   `./mock` exports `enableContextMock` and `ContextMockConfigurator` — a `ContextModuleConfigurator` backed by an in-memory pool instead of a real client. Only the data source is substituted; `validateContext`, `resolveContext`, and parent-context propagation all still run through the real `ContextProvider`:
-
+  
   ```typescript
-  import { enableContextMock } from "@equinor/fusion-framework-module-context/mock";
-
+  import { enableContextMock } from '@equinor/fusion-framework-module-context/mock';
+  
   enableContextMock(configurator, (mock) => {
-    mock.setCurrentContext({
-      id: "my-ctx",
-      type: { id: "ProjectMaster" },
-      value: {},
-    });
+    mock.setCurrentContext({ id: 'my-ctx', type: { id: 'ProjectMaster' }, value: {} });
   });
   ```
-
+  
   `ContextMockConfigurator` also has `setContexts`, `addContext`, `setRelatedContexts` for the common cases, and `setResolver` as an escape hatch for custom resolution. Seeding an initial context this way overrides `resolveInitialContext` directly, so a test doesn't need a fake navigation module or parent framework instance just to start an app with a known context selected.
-
+  
   `./mock/fixtures` exports `createContextItems` and `createContextItemFactory`, generating realistic `ContextItem`s via an optional `@faker-js/faker` peer dependency — kept on a separate entry point so `enableContextMock` never pulls faker in for tests that don't need it:
-
+  
   ```typescript
-  import { createContextItems } from "@equinor/fusion-framework-module-context/mock/fixtures";
-
-  const [project] = createContextItems([{ type: "ProjectMaster" }]);
+  import { createContextItems } from '@equinor/fusion-framework-module-context/mock/fixtures';
+  
+  const [project] = createContextItems([{ type: 'ProjectMaster' }]);
   ```
-
+  
   Also exports `parseContextItem` from the `./utils` subpath (parses a raw API context entity into a `ContextItem`), and reorganizes internal selector/configurator files without changing any existing public export.
 
 ### Patch Changes
 
-- e8aae1f: Internal: publish every package on the `next` pre-release tag so the whole framework can be installed as a coherent set.
-
-  Packages without their own changes are bumped only to receive a `-next.N` version and the `next` dist-tag on npm. Install with:
-
-  ```bash
-  pnpm add @equinor/fusion-framework-react-app@next
-  ```
-
-- 2836e0b: Declare `@equinor/fusion-framework-module-telemetry` as an optional peer dependency.
-
+- f663b46: Restructure documentation so the README is an entry point rather than a manual, matching the convention already used by `@equinor/fusion-framework-module` and `@equinor/fusion-framework-module-http`.
+  
+  Long-form content moves into `docs/data-model.md` (the `ContextItem`/`ContextItemType` shape and query/related parameter types), `docs/lifecycle.md` (setting/resolving context, initial-context resolution, parent/child propagation), and `docs/recipes.md` (OData query parameters, path rewriting, accepting a family of related context types, skipping the default initial-context lookup, custom search errors). The README keeps the elevator pitch, a "How it fits together" section on module dependencies, and a documentation table linking to the rest.
+- f663b46: Fix `ContextModule.postInitialize` logging a `console.warn` for the valid "no initial context" case (no context in the path and no parent context). The default `resolveInitialContext` resolver used RxJS `first()` without a default value, so completing with no emissions threw an `EmptyError` that got logged as if resolution had actually failed. `first()` now falls back to `undefined`, so a genuinely empty result completes silently and only real resolution failures are logged.
+- f663b46: Declare `@equinor/fusion-framework-module-telemetry` as an optional peer dependency.
+  
   The context module imports `TelemetryLevel`/`TelemetryScope` at runtime to report context
   resolution failures when a telemetry module is registered, but telemetry was previously
   undeclared outside of this package's own dev dependencies. A consumer installing only
   `@equinor/fusion-framework-module-context` without telemetry could fail to resolve this
   import at runtime.
 
-- 2836e0b: Restructure documentation so the README is an entry point rather than a manual, matching the convention already used by `@equinor/fusion-framework-module` and `@equinor/fusion-framework-module-http`.
-
-  Long-form content moves into `docs/data-model.md` (the `ContextItem`/`ContextItemType` shape and query/related parameter types), `docs/lifecycle.md` (setting/resolving context, initial-context resolution, parent/child propagation), and `docs/recipes.md` (OData query parameters, path rewriting, accepting a family of related context types, skipping the default initial-context lookup, custom search errors). The README keeps the elevator pitch, a "How it fits together" section on module dependencies, and a documentation table linking to the rest.
-
-- 2836e0b: Fix `ContextModule.postInitialize` logging a `console.warn` for the valid "no initial context" case (no context in the path and no parent context). The default `resolveInitialContext` resolver used RxJS `first()` without a default value, so completing with no emissions threw an `EmptyError` that got logged as if resolution had actually failed. `first()` now falls back to `undefined`, so a genuinely empty result completes silently and only real resolution failures are logged.
-- Updated dependencies [e8aae1f]
-- Updated dependencies [2836e0b]
-- Updated dependencies [2836e0b]
-- Updated dependencies [2836e0b]
-- Updated dependencies [2836e0b]
-- Updated dependencies [2836e0b]
-  - @equinor/fusion-framework-module@6.1.3-next.0
-  - @equinor/fusion-framework-module-telemetry@8.0.0-next.0
-  - @equinor/fusion-query@7.0.4-next.0
-
 ## 8.0.3
 
 ### Patch Changes

package/dist/esm/version.js

@@ -1,3 +1,3 @@
 // Generated by genversion.
-export const version = '9.0.0-next.0';
+export const version = '9.0.0';
 //# sourceMappingURL=version.js.map

package/dist/esm/version.js.map

@@ -1 +1 @@
-{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAAA,2BAA2B;AAC3B,MAAM,CAAC,MAAM,OAAO,GAAG,cAAc,CAAC"}
+{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAAA,2BAA2B;AAC3B,MAAM,CAAC,MAAM,OAAO,GAAG,OAAO,CAAC"}