Skip to content

fix(deps): update @deck.gl/core requirement from ^8.9.34 to ^8.9.36 #1179

fix(deps): update @deck.gl/core requirement from ^8.9.34 to ^8.9.36

fix(deps): update @deck.gl/core requirement from ^8.9.34 to ^8.9.36 #1179

Triggered via pull request May 19, 2024 19:28
Status Success
Total duration 1m 17s
Artifacts

codeql.yml

on: pull_request
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

12 errors
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)
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)
src/layers/deck.gl/VLayerDeckArc.vue#L19
Unexpected any. Specify a different type (@typescript-eslint/no-explicit-any)
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)
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)
src/layers/deck.gl/VLayerDeckGeojson.vue#L6
Unable to resolve path to module 'geojson' (import/no-unresolved)
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)
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)
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)
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)
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)
vite-env.d.ts#L5
Unexpected any. Specify a different type (@typescript-eslint/no-explicit-any)