Skip to content

feat: new dashboard experience #210

feat: new dashboard experience

feat: new dashboard experience #210

Triggered via pull request September 18, 2024 00:18
Status Success
Total duration 1m 29s
Artifacts

frontend-tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

15 warnings
frontends/analytics/src/components/charts/HeadQueries.tsx#L24
[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/LowConfidenceQueries.tsx#L24
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/LowConfidenceQueries.tsx#L35
[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/NoResultQueries.tsx#L23
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/NoResultQueries.tsx#L36
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/NoResultQueries.tsx#L37
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/NoResultQueries.tsx#L45
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/NoResultQueries.tsx#L56
[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/components/charts/RagQueries.tsx#L145
[solid/reactivity] The reactive variable 'columns' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L31
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L41
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L42
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L52
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
eslint
The following actions uses node12 which is deprecated and will be forced to run on node16: ataylorme/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
eslint
The following actions use a deprecated Node.js version and will be forced to run on node20: ataylorme/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/