@open-pioneer/map-test-utils 1.5.0-dev.20260917081843 → 1.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +40 -39
  2. package/package.json +3 -3
package/CHANGELOG.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # @open-pioneer/map-test-utils
2
2
 
3
- ## 1.5.0-dev.20260917081843
3
+ ## 1.5.0
4
4
 
5
5
  ### Minor Changes
6
6
 
@@ -8,42 +8,43 @@
8
8
  - 0d9a9d0: The map initialization has been adjusted to fix the map view initialization if initial view is configured with extent.
9
9
  This change affects the order and timing of the map's initialization.
10
10
 
11
- The timing changes might affect early map interactions or tests:
12
- To wait until the map is actually being rendered (and thus fully initialized), you can use the map model's existing `whenDisplayed()` method.
13
- The new test helper function `waitForMapRender` is provided from (`@open-pioneer/map-test-utils`) to wait in tests for the map view to be completely initialized.
11
+ The timing changes might affect early map interactions or tests:
12
+ To wait until the map is actually being rendered (and thus fully initialized), you can use the map model's existing `whenDisplayed()` method.
13
+ The new test helper function `waitForMapRender` is provided from (`@open-pioneer/map-test-utils`) to wait in tests for the map view to be completely initialized.
14
14
 
15
+ - a186f5d: Update core packages to 4.8.0.
15
16
  - ebda251: Add new properties for topmost layers and base layers in `MapConfig`.
16
17
 
17
- - With `MapConfig.topmostLayers` topmost layers can now be defined in the initial map setup.
18
- - Base layers can now be defined in the initial map setup with the `MapConfig.baseLayers` property
19
-
20
- We recommend using the `baseLayers` property instead of `isBaseLayer: true` for new apps.
21
-
22
- ```typescript
23
- export class MapConfigProviderImpl implements MapConfigProvider {
24
- mapId = MAP_ID;
25
-
26
- async getMapConfig({ layerFactory }: MapConfigProviderOptions): Promise<MapConfig> {
27
- return {
28
- initialView: {...},
29
- projection: "EPSG:25832",
30
- baseLayers: [
31
- //all base layers
32
- layerFactory.create(...)
33
- ],
34
- layers: [
35
- //all other operational layers
36
- layerFactory.create(...),
37
- layerFactory.create(...)
38
- ],
39
- topmostLayers: [
40
- //all operational highlight layers
41
- layerFactory.create(...)
42
- ]
43
- };
44
- }
45
- }
46
- ```
18
+ - With `MapConfig.topmostLayers` topmost layers can now be defined in the initial map setup.
19
+ - Base layers can now be defined in the initial map setup with the `MapConfig.baseLayers` property
20
+
21
+ We recommend using the `baseLayers` property instead of `isBaseLayer: true` for new apps.
22
+
23
+ ```typescript
24
+ export class MapConfigProviderImpl implements MapConfigProvider {
25
+ mapId = MAP_ID;
26
+
27
+ async getMapConfig({ layerFactory }: MapConfigProviderOptions): Promise<MapConfig> {
28
+ return {
29
+ initialView: {...},
30
+ projection: "EPSG:25832",
31
+ baseLayers: [
32
+ //all base layers
33
+ layerFactory.create(...)
34
+ ],
35
+ layers: [
36
+ //all other operational layers
37
+ layerFactory.create(...),
38
+ layerFactory.create(...)
39
+ ],
40
+ topmostLayers: [
41
+ //all operational highlight layers
42
+ layerFactory.create(...)
43
+ ]
44
+ };
45
+ }
46
+ }
47
+ ```
47
48
 
48
49
  ### Patch Changes
49
50
 
@@ -91,8 +92,8 @@
91
92
 
92
93
  - 14c484e: Deprecate `createServiceOptions()` function.
93
94
 
94
- This function was previously used in tests to mock the map registry for a react component under test.
95
- This is no longer necessary because our react components now receive the map model directly (no lookup is done anymore).
95
+ This function was previously used in tests to mock the map registry for a react component under test.
96
+ This is no longer necessary because our react components now receive the map model directly (no lookup is done anymore).
96
97
 
97
98
  ### Minor Changes
98
99
 
@@ -134,9 +135,9 @@
134
135
  ### Minor Changes
135
136
 
136
137
  - 2fa8020: Update trails core package dependencies.
137
- - Also updates Chakra UI to the latest 2.x version and Chakra React Select to version 5.
138
- - Removes any obsolete references to `@chakra-ui/system`.
139
- This dependency seems to be no longer required and may lead to duplicate packages in your dependency tree.
138
+ - Also updates Chakra UI to the latest 2.x version and Chakra React Select to version 5.
139
+ - Removes any obsolete references to `@chakra-ui/system`.
140
+ This dependency seems to be no longer required and may lead to duplicate packages in your dependency tree.
140
141
 
141
142
  ### Patch Changes
142
143
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "type": "module",
3
3
  "name": "@open-pioneer/map-test-utils",
4
- "version": "1.5.0-dev.20260917081843",
4
+ "version": "1.5.0",
5
5
  "description": "This package is an internal support package for testing map-related UI components.",
6
6
  "keywords": [
7
7
  "open-pioneer-trails"
@@ -15,8 +15,8 @@
15
15
  },
16
16
  "dependencies": {
17
17
  "@conterra/reactivity-core": "^0.8.8",
18
- "@open-pioneer/map": "1.5.0-dev.20260917081843",
19
- "@open-pioneer/test-utils": "4.8.0-dev.20260910101405",
18
+ "@open-pioneer/map": "1.5.0",
19
+ "@open-pioneer/test-utils": "^4.8.0",
20
20
  "@testing-library/react": "^16.3.3",
21
21
  "ol": "^10.10.0"
22
22
  },