Skip to content

[24.0] Fix submitted value in workflow run form if data is constrained by tag filter #6103

[24.0] Fix submitted value in workflow run form if data is constrained by tag filter

[24.0] Fix submitted value in workflow run form if data is constrained by tag filter #6103

Triggered via pull request May 22, 2024 13:15
Status Success
Total duration 2m 5s
Artifacts

js_lint.yaml

on: pull_request
Matrix: client-unit-test
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
client-unit-test (18)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
client-unit-test (18): client/src/api/histories.archived.ts#L83
Do not use "@ts-ignore" because it alters compilation errors
client-unit-test (18): client/src/api/schema/__mocks__/fetcher.ts#L17
Unexpected any. Specify a different type
client-unit-test (18): client/src/api/schema/__mocks__/fetcher.ts#L22
Unexpected any. Specify a different type
client-unit-test (18): client/src/api/schema/__mocks__/fetcher.ts#L55
Unexpected any. Specify a different type
client-unit-test (18): client/src/api/schema/__mocks__/fetcher.ts#L86
Unexpected any. Specify a different type
client-unit-test (18): client/src/api/schema/__mocks__/fetcher.ts#L87
Unexpected any. Specify a different type
client-unit-test (18): client/src/components/ActivityBar/ActivityBar.vue#L129
Visible, non-interactive elements should not have an interactive handler
client-unit-test (18): client/src/components/ActivityBar/ActivityItem.vue#L57
Visible, non-interactive elements with click handlers must have at least one keyboard listener
client-unit-test (18): client/src/components/ActivityBar/ActivityItem.vue#L57
Visible, non-interactive elements should not have an interactive handler
client-unit-test (18): client/src/components/Alert.vue#L1
Component name "Alert" should always be multi-word