Skip to content

Changes to permission store actions for mapping permissions #1597

Changes to permission store actions for mapping permissions

Changes to permission store actions for mapping permissions #1597

Triggered via push February 7, 2024 20:27
Status Failure
Total duration 35s
Artifacts 1

unit-tests.yaml

on: push
Matrix: Unit Tests (Frontend)
Matrix: Unit Tests (App)
Publish to Code Climate
0s
Publish to Code Climate
Fit to window
Zoom out
Zoom in

Annotations

30 errors and 6 warnings
Unit Tests (Frontend) (20.x)
Parameter 'event' implicitly has an 'any' type.
Unit Tests (Frontend) (20.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (20.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (20.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (20.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (20.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (20.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (20.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (20.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (20.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (16.x)
Parameter 'event' implicitly has an 'any' type.
Unit Tests (Frontend) (16.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (16.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (16.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (16.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (16.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (16.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (16.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (16.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (16.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (18.x)
Parameter 'event' implicitly has an 'any' type.
Unit Tests (Frontend) (18.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (18.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (18.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (18.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (18.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (18.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (18.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (18.x)
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UserPermissions'.
Unit Tests (Frontend) (18.x)
Object is possibly 'undefined'.
Unit Tests (Frontend) (20.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit Tests (Frontend) (16.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit Tests (App) (18.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit Tests (App) (20.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit Tests (Frontend) (18.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit Tests (App) (16.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
coverage-app Expired
75.8 KB