Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps-dev): update @typescript-eslint/eslint-plugin requirement from ^7.9.0 to ^7.16.1 #1927

Closed
wants to merge 1 commit into from

chore(deps-dev): update @typescript-eslint/eslint-plugin requirement

28d8edf
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Closed

chore(deps-dev): update @typescript-eslint/eslint-plugin requirement from ^7.9.0 to ^7.16.1 #1927

chore(deps-dev): update @typescript-eslint/eslint-plugin requirement
28d8edf
Select commit
Loading
Failed to load commit list.
GitHub Actions / ESLint failed Jul 15, 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 

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

See this annotation in the file changed.

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

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)
View more details on GitHub Actions