Skip to content

Split variant flags #677

Split variant flags

Split variant flags #677

Triggered via pull request September 6, 2024 16:57
Status Failure
Total duration 31s
Artifacts

graphql-api-ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L47
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L56
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L118
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L145
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L154
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L190
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L199
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L251
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L276
["variantFlags"] is better written in dot notation
Checks: graphql-api/src/queries/variant-datasets/shared/flags.spec.ts#L285
["variantFlags"] is better written in dot notation
Checks
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Checks
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, pnpm/action-setup@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/