Skip to content

Make Navbar responsive through use of MUI drawer component #449

Make Navbar responsive through use of MUI drawer component

Make Navbar responsive through use of MUI drawer component #449

Triggered via pull request October 18, 2023 00:03
Status Failure
Total duration 2m 36s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

pr.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 5 warnings
type-check: src/components/navbar/NavBar.tsx#L108
Type 'Element' is not assignable to type 'string'.
type-check: src/components/navbar/NavBar.tsx#L141
Type 'Element' is not assignable to type 'string'.
type-check
Process completed with exit code 2.
type-check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint: src/components/uploadPicture/uploadImage.tsx#L120
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element
lint: src/components/uploadedFile/uploadedFile.tsx#L26
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element