chore(deps-dev): Bump fetch-mock from 7.7.3 to 11.1.4 #1539
dependabot[bot]Annotations
1 error and 13 warnings
|
Unit tests
Process completed with exit code 1.
|
|
prettier
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Unit tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
lint:
app/components/Comments/ModalFlag.jsx#L15
Unused state field: 'error'
|
|
lint:
app/components/Comments/ModalFlag.jsx#L22
Unused state field: 'error'
|
|
lint:
app/components/FormUtils/ControlInputWithLabel.jsx#L5
Component definition is missing display name
|
|
lint:
app/components/FormUtils/ControlInputWithLabel.jsx#L7
Form label must have ALL of the following types of associated control: nesting, id
|
|
lint:
app/components/FormUtils/FieldWithButton.jsx#L6
Component definition is missing display name
|
|
lint:
app/components/FormUtils/FieldWithLabelAddon.jsx#L8
Form label must have ALL of the following types of associated control: nesting, id
|
|
lint:
app/components/FormUtils/Input.jsx#L4
Component definition is missing display name
|
|
lint:
app/components/LoggedInUser/UserProvider.jsx#L176
Component definition is missing display name
|
|
lint:
app/components/Modal/Modal.jsx#L28
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
|
lint:
app/components/Modal/Modal.jsx#L28
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|