Feature/DF-861: Geospatial component #1628
Annotations
15 errors and 21 warnings
|
Unit tests (Node 24)
Process completed with exit code 1.
|
|
Location field formatting › GeospatialField › formats for summary display:
src/server/plugins/engine/components/helpers/components.test.ts#L261
expect(received).toBe(expected) // Object.is equality
Expected: "Added 4 features"
Received: "Added 4 locations"
at Object.toBe (src/server/plugins/engine/components/helpers/components.test.ts:261:22)
|
|
Location field formatting › GeospatialField › formats for email output as single value:
src/server/plugins/engine/components/helpers/components.test.ts#L243
expect(received).toBe(expected) // Object.is equality
- Expected - 1
+ Received + 1
- Added 4 features
+ Added 4 locations
↵
at Object.toBe (src/server/plugins/engine/components/helpers/components.test.ts:243:22)
|
|
Maps Client JS › Geospatial component › Map initialisation › marker added:
test/client/javascripts/map.test.js#L1051
expect(received).toEqual(expected) // deep equality
- Expected - 3
+ Received + 3
@@ -98,19 +98,19 @@
"type": "Feature",
},
Object {
"geometry": Object {
"coordinates": Array [
- -2.0868919921875886,
- 53.896834237148596,
+ -2.086892,
+ 53.8968342,
],
"type": "Point",
},
"id": Any<String>,
"properties": Object {
"centroidGridReference": "SD 94387 44521",
"coordinateGridReference": "SD 94387 44521",
- "description": "New point",
+ "description": "",
},
"type": "Feature",
},
]
at Object.toEqual (test/client/javascripts/map.test.js:1051:51)
|
|
Maps Client JS › Geospatial component › Map initialisation › drawing created:
test/client/javascripts/map.test.js#L885
expect(received).toBe(expected) // Object.is equality
- Expected - 1
+ Received + 1
@@ -122,11 +122,11 @@
]
]
]
},
"properties": {
- "description": "New shape",
+ "description": "",
"coordinateGridReference": "SD 94387 44521",
"centroidGridReference": "SE 16533 42846"
}
}
]
at Object.toBe (test/client/javascripts/map.test.js:885:39)
|
|
Unit tests (Node 23)
Process completed with exit code 1.
|
|
Location field formatting › GeospatialField › formats for summary display:
src/server/plugins/engine/components/helpers/components.test.ts#L261
expect(received).toBe(expected) // Object.is equality
Expected: "Added 4 features"
Received: "Added 4 locations"
at Object.toBe (src/server/plugins/engine/components/helpers/components.test.ts:261:22)
|
|
Location field formatting › GeospatialField › formats for email output as single value:
src/server/plugins/engine/components/helpers/components.test.ts#L243
expect(received).toBe(expected) // Object.is equality
- Expected - 1
+ Received + 1
- Added 4 features
+ Added 4 locations
↵
at Object.toBe (src/server/plugins/engine/components/helpers/components.test.ts:243:22)
|
|
Maps Client JS › Geospatial component › Map initialisation › marker added:
test/client/javascripts/map.test.js#L1051
expect(received).toEqual(expected) // deep equality
- Expected - 3
+ Received + 3
@@ -98,19 +98,19 @@
"type": "Feature",
},
Object {
"geometry": Object {
"coordinates": Array [
- -2.0868919921875886,
- 53.896834237148596,
+ -2.086892,
+ 53.8968342,
],
"type": "Point",
},
"id": Any<String>,
"properties": Object {
"centroidGridReference": "SD 94387 44521",
"coordinateGridReference": "SD 94387 44521",
- "description": "New point",
+ "description": "",
},
"type": "Feature",
},
]
at Object.toEqual (test/client/javascripts/map.test.js:1051:51)
|
|
Maps Client JS › Geospatial component › Map initialisation › drawing created:
test/client/javascripts/map.test.js#L885
expect(received).toBe(expected) // Object.is equality
- Expected - 1
+ Received + 1
@@ -122,11 +122,11 @@
]
]
]
},
"properties": {
- "description": "New shape",
+ "description": "",
"coordinateGridReference": "SD 94387 44521",
"centroidGridReference": "SE 16533 42846"
}
}
]
at Object.toBe (test/client/javascripts/map.test.js:885:39)
|
|
Unit tests (Node 22)
Process completed with exit code 1.
|
|
Location field formatting › GeospatialField › formats for summary display:
src/server/plugins/engine/components/helpers/components.test.ts#L261
expect(received).toBe(expected) // Object.is equality
Expected: "Added 4 features"
Received: "Added 4 locations"
at Object.toBe (src/server/plugins/engine/components/helpers/components.test.ts:261:22)
|
|
Location field formatting › GeospatialField › formats for email output as single value:
src/server/plugins/engine/components/helpers/components.test.ts#L243
expect(received).toBe(expected) // Object.is equality
- Expected - 1
+ Received + 1
- Added 4 features
+ Added 4 locations
↵
at Object.toBe (src/server/plugins/engine/components/helpers/components.test.ts:243:22)
|
|
Maps Client JS › Geospatial component › Map initialisation › marker added:
test/client/javascripts/map.test.js#L1051
expect(received).toEqual(expected) // deep equality
- Expected - 3
+ Received + 3
@@ -98,19 +98,19 @@
"type": "Feature",
},
Object {
"geometry": Object {
"coordinates": Array [
- -2.0868919921875886,
- 53.896834237148596,
+ -2.086892,
+ 53.8968342,
],
"type": "Point",
},
"id": Any<String>,
"properties": Object {
"centroidGridReference": "SD 94387 44521",
"coordinateGridReference": "SD 94387 44521",
- "description": "New point",
+ "description": "",
},
"type": "Feature",
},
]
at Object.toEqual (test/client/javascripts/map.test.js:1051:51)
|
|
Maps Client JS › Geospatial component › Map initialisation › drawing created:
test/client/javascripts/map.test.js#L885
expect(received).toBe(expected) // Object.is equality
- Expected - 1
+ Received + 1
@@ -122,11 +122,11 @@
]
]
]
},
"properties": {
- "description": "New shape",
+ "description": "",
"coordinateGridReference": "SD 94387 44521",
"centroidGridReference": "SE 16533 42846"
}
}
]
at Object.toBe (test/client/javascripts/map.test.js:885:39)
|
|
Build (Node 23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
EditorConfig (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Stylelint (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Stylelint (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
EditorConfig (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Stylelint (Node 23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TypeScript compiler (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
EditorConfig (Node 23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Prettier (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TypeScript compiler (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TypeScript compiler (Node 23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Prettier (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Prettier (Node 23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ESLint (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ESLint (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ESLint (Node 23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests (Node 23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Unit tests coverage (Node 22)
|
853 KB |
sha256:64ca6737e805c821d5a58045524ed795bc6be825081ea88dab5d69bf8ae0ba5c
|
|
|
Unit tests coverage (Node 23)
|
852 KB |
sha256:8ff19066bbbfaca30b54c14f0089665f2cbbd8710e7a4f1005dd80aef3349945
|
|
|
Unit tests coverage (Node 24)
|
853 KB |
sha256:dd039d5b5677be6f7b4c361e7e749658fc1d8a37d8a203966397fed3374e5cc5
|
|