backend fixes #186

Sign in to view logs

Triggered via pull request October 28, 2023 16:02

ygupta17

synchronize #72

yash/65-fix-root-user-script

Status Success

Total duration 1m 30s

Artifacts –

lint.yml

on: pull_request

Annotations

1 error and 7 warnings

src/server/mongodb/actions/User.js#L1

There are issues with this file's formatting, please run Prettier to fix the errors

src/pages/reset_password/[token].js#L58

Do not use `<img>` element. Use `<Image />` from `next/image` instead. See: https://nextjs.org/docs/messages/no-img-element (@next/next/no-img-element)

src/screens/Member/MemberProfile.js#L173

Do not use `<img>` element. Use `<Image />` from `next/image` instead. See: https://nextjs.org/docs/messages/no-img-element (@next/next/no-img-element)

src/screens/Member/MemberProfile.js#L176

Do not use `<img>` element. Use `<Image />` from `next/image` instead. See: https://nextjs.org/docs/messages/no-img-element (@next/next/no-img-element)

src/screens/Member/MemberProfile.js#L209

Do not use `<img>` element. Use `<Image />` from `next/image` instead. See: https://nextjs.org/docs/messages/no-img-element (@next/next/no-img-element)

src/screens/Member/SuccessBox/SuccessBox.js#L28

Do not use `<img>` element. Use `<Image />` from `next/image` instead. See: https://nextjs.org/docs/messages/no-img-element (@next/next/no-img-element)

src/screens/Member/SuccessBox/SuccessBox.js#L28

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

Run linters

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/