Bump typescript-eslint from 7.1.0 to 8.6.0 in /frontend #1837
Triggered via pull request
September 17, 2024 15:40
Status
Failure
Total duration
1m 48s
Artifacts
–
action-intall-and-test.yml
on: pull_request
install-and-test
1m 39s
Annotations
10 errors and 10 warnings
install-and-test:
frontend/src/components/Layout/useExternalScripts.tsx#L120
'e' is defined but never used
|
install-and-test:
frontend/src/components/Map/components/TileLayerExtended/index.tsx#L83
'e' is defined but never used
|
install-and-test:
frontend/src/components/pages/details/__tests__/Details.test.tsx#L37
A `require()` style import is forbidden
|
install-and-test:
frontend/src/components/pages/details/components/DetailsViewPoints/DetailsViewPoints.tsx#L106
Expected an assignment or function call and instead saw an expression
|
install-and-test:
frontend/src/components/pages/details/components/DetailsViewPoints/DetailsViewPoints.tsx#L109
Expected an assignment or function call and instead saw an expression
|
install-and-test:
frontend/src/components/pages/search/hooks/useTrekResults.ts#L32
Expected an assignment or function call and instead saw an expression
|
install-and-test:
frontend/src/components/pages/search/hooks/useTrekResults.ts#L33
Expected an assignment or function call and instead saw an expression
|
install-and-test:
frontend/src/components/pages/search/hooks/useTrekResults.ts#L34
Expected an assignment or function call and instead saw an expression
|
install-and-test:
frontend/src/modules/filters/networks/connector.ts#L10
'e' is defined but never used
|
install-and-test:
frontend/src/modules/filters/organizer/connector.ts#L10
'e' is defined but never used
|
install-and-test:
frontend/src/components/Header/Header.tsx#L45
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
install-and-test:
frontend/src/components/ImageWithLegend/index.tsx#L36
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
install-and-test:
frontend/src/components/Layout/useExternalScripts.tsx#L26
Unexpected any. Specify a different type
|
install-and-test:
frontend/src/components/Map/DetailsMap/DetailsMap.tsx#L163
React Hook useEffect has missing dependencies: 'props' and 'reportVisibility'. Either include them or remove the dependency array. However, 'props' will change when *any* prop changes, so the preferred fix is to destructure the 'props' object outside of the useEffect call and refer to those specific props inside useEffect
|
install-and-test:
frontend/src/components/Map/components/HoverableMarker.tsx#L53
React Hook useMemo has a missing dependency: 'props'. Either include it or remove the dependency array
|
install-and-test:
frontend/src/components/Map/components/TileLayerExtended/index.tsx#L129
React Hook useEffect has missing dependencies: 'loadLayer' and 'rangeZoom'. Either include them or remove the dependency array
|
install-and-test:
frontend/src/components/Map/components/TileLayerExtended/index.tsx#L140
React Hook useEffect has a missing dependency: 'options?.attribution'. Either include it or remove the dependency array
|
install-and-test:
frontend/src/components/pages/details/Details.tsx#L709
React Hook useMemo has missing dependencies: 'anchors', 'handleViewPointClick', 'hasNavigator', 'sectionRef', 'sections', and 'setMapId'. Either include them or remove the dependency array
|
install-and-test:
frontend/src/components/pages/details/components/DetailsReservationWidget/DetailsReservationWidget.tsx#L60
React Hook useEffect has a missing dependency: 'isMounted'. Either include it or remove the dependency array
|
install-and-test:
frontend/src/components/pages/home/components/BannerCarousel/BannerCarousel.tsx#L24
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|