fix(deps): bump the actions-minor group across 1 directory with 2 updates #1079

Sign in to view logs

GitHub Actions / ESLint failed Jul 7, 2024 in 0s

12 errors

ESLint found 12 errors

Annotations

Check failure on line 2 in src/layers/deck.gl/VLayerDeckArc.vue

github-actions / ESLint

src/layers/deck.gl/VLayerDeckArc.vue#L2

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)

Check failure on line 4 in src/layers/deck.gl/VLayerDeckArc.vue

github-actions / ESLint

src/layers/deck.gl/VLayerDeckArc.vue#L4

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)

Check failure on line 19 in src/layers/deck.gl/VLayerDeckArc.vue

github-actions / ESLint

src/layers/deck.gl/VLayerDeckArc.vue#L19

Unexpected any. Specify a different type (@typescript-eslint/no-explicit-any)

Check failure on line 2 in src/layers/deck.gl/VLayerDeckGeojson.vue

github-actions / ESLint

src/layers/deck.gl/VLayerDeckGeojson.vue#L2

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)

Check failure on line 4 in src/layers/deck.gl/VLayerDeckGeojson.vue

github-actions / ESLint

src/layers/deck.gl/VLayerDeckGeojson.vue#L4

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)

Check failure on line 6 in src/layers/deck.gl/VLayerDeckGeojson.vue

github-actions / ESLint

src/layers/deck.gl/VLayerDeckGeojson.vue#L6

Unable to resolve path to module 'geojson' (import/no-unresolved)

Check failure on line 14 in src/map/VMap.vue

github-actions / ESLint

src/map/VMap.vue#L14

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)

Check failure on line 4 in test/setup/index.ts

github-actions / ESLint

test/setup/index.ts#L4

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)

Check failure on line 7 in test/setup/index.ts

github-actions / ESLint

test/setup/index.ts#L7

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)

Check failure on line 5 in vite-env.d.ts

github-actions / ESLint

vite-env.d.ts#L5

Don't use `{}` as a type. `{}` actually means "any non-nullish value".
- If you want a type meaning "any object", you probably want `object` instead.
- If you want a type meaning "any value", you probably want `unknown` instead.
- If you want a type meaning "empty object", you probably want `Record<string, never>` instead.
- If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead (@typescript-eslint/ban-types)

Check failure on line 5 in vite-env.d.ts

github-actions / ESLint

vite-env.d.ts#L5

Don't use `{}` as a type. `{}` actually means "any non-nullish value".
- If you want a type meaning "any object", you probably want `object` instead.
- If you want a type meaning "any value", you probably want `unknown` instead.
- If you want a type meaning "empty object", you probably want `Record<string, never>` instead.
- If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead (@typescript-eslint/ban-types)

Check failure on line 5 in vite-env.d.ts

github-actions / ESLint

vite-env.d.ts#L5

Unexpected any. Specify a different type (@typescript-eslint/no-explicit-any)

View more details on GitHub Actions