Skip to content

chore(deps-dev): bump @typescript-eslint/eslint-plugin from 7.18.0 to 8.1.0 #1209

chore(deps-dev): bump @typescript-eslint/eslint-plugin from 7.18.0 to 8.1.0

chore(deps-dev): bump @typescript-eslint/eslint-plugin from 7.18.0 to 8.1.0 #1209

GitHub Actions / ESLint failed Aug 12, 2024 in 0s

12 errors

ESLint found 12 errors

Annotations

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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions 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

See this annotation in the file changed.

@github-actions github-actions / ESLint

vite-env.d.ts#L5

The `{}` ("empty object") type allows any non-nullish value, including literals like `0` and `""`.
- If that's what you want, disable this lint rule with an inline comment or configure the 'allowObjectTypes' rule option.
- 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 (@typescript-eslint/no-empty-object-type)

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

See this annotation in the file changed.

@github-actions github-actions / ESLint

vite-env.d.ts#L5

The `{}` ("empty object") type allows any non-nullish value, including literals like `0` and `""`.
- If that's what you want, disable this lint rule with an inline comment or configure the 'allowObjectTypes' rule option.
- 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 (@typescript-eslint/no-empty-object-type)

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

See this annotation in the file changed.

@github-actions github-actions / ESLint

vite-env.d.ts#L5

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