Skip to content
Run graphql CI

Graphql, Web: store connection map #335

Sign in to view logs

Graphql, Web: store connection map

Graphql, Web: store connection map #335

Triggered via pull request January 31, 2025 00:45
@liuliu-devliuliu-dev
synchronize #357
liuliu/store-connection-map
Status Failure
Total duration 45s
Artifacts –

ci-graphql.yaml

on: pull_request
ci
34s
ci
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 10 warnings
ci: graphql-server/src/connections/connection.provider.ts#L44
Unnecessary conditional, value is always falsy
ci: graphql-server/src/connections/connection.provider.ts#L75
Use object destructuring
ci: graphql-server/src/connections/connection.provider.ts#L92
Use object destructuring
ci: graphql-server/src/queryFactory/base.ts#L35
Unexpected block statement surrounding arrow body; move the returned value immediately after the `=>`
ci
Process completed with exit code 1.
ci: graphql-server/src/branches/branch.resolver.ts#L109
Unexpected console statement
ci: graphql-server/src/connections/connection.provider.ts#L40
Unexpected console statement
ci: graphql-server/src/databases/database.resolver.ts#L126
Unexpected console statement
ci: graphql-server/src/databases/database.resolver.ts#L128
Unexpected console statement
ci: graphql-server/src/fileStore/fileStore.service.ts#L8
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
ci: graphql-server/src/fileStore/fileStore.service.ts#L28
Unexpected console statement
ci: graphql-server/src/fileStore/fileStore.service.ts#L44
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
ci: graphql-server/src/fileStore/fileStore.service.ts#L45
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
ci: graphql-server/src/main.ts#L24
Unexpected console statement
ci: graphql-server/src/queryFactory/dolt/index.ts#L403
Unexpected console statement