Skip to content

Merge pull request #381 from RunTerror/feat/beacon-dev #515

Merge pull request #381 from RunTerror/feat/beacon-dev

Merge pull request #381 from RunTerror/feat/beacon-dev #515

Triggered via push September 28, 2024 20:04
Status Failure
Total duration 28s
Artifacts

lint.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
build (16.x): graphql/resolvers.js#L12
'parseBeaconObject' is assigned a value but never used
build (16.x): graphql/resolvers.js#L13
'landmark' is assigned a value but never used
build (16.x): graphql/resolvers.js#L251
Unexpected empty object pattern
build (16.x): graphql/resolvers.js#L276
Unexpected empty object pattern
build (16.x): graphql/resolvers.js#L283
'pubsub' is defined but never used
build (16.x): graphql/resolvers.js#L353
Empty block statement
build (16.x): graphql/resolvers.js#L644
'newLeaderID' is defined but never used
build (16.x): graphql/resolvers.js#L644
'user' is defined but never used
build (16.x): graphql/resolvers.js#L645
'beacon' is assigned a value but never used
build (16.x): parsing.js#L53
Empty block statement
build (16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (16.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/