Skip to content

Fixes #37900 - Allow syncing templates through HTTP proxy #22

Fixes #37900 - Allow syncing templates through HTTP proxy

Fixes #37900 - Allow syncing templates through HTTP proxy #22

Triggered via pull request October 18, 2024 17:19
Status Failure
Total duration 1m 35s
Artifacts

js_ci.yml

on: pull_request
Matrix: test_js
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
test_js (12): webpack/components/NewTemplateSync/components/ProxySettingField.js#L11
Replace `⏎const·ProxySettingField·=·({·setting,·resetField,·field,·form,·fieldName·})·=>` with `const·ProxySettingField·=·({·setting,·resetField,·field,·form,·fieldName·})·=>·(`
test_js (12): webpack/components/NewTemplateSync/components/ProxySettingFields.js#L36
Unexpected block statement surrounding arrow body; move the returned value immediately after the `=>`
test_js (12)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test_js (12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/