Feat: safe overviews endpoint #322
katspaughAnnotations
2 errors and 1 warning
|
@typescript-eslint/ban-types:
src/types/api.ts#L427
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.
* [SUGGESTION] Replace `{}` with `object`.
* [SUGGESTION] Replace `{}` with `unknown`.
* [SUGGESTION] Replace `{}` with `Record<string, never>`.
* [SUGGESTION] Replace `{}` with `NonNullable<unknown>`.
|
|
@typescript-eslint/ban-types:
src/types/api.ts#L1115
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.
* [SUGGESTION] Replace `{}` with `object`.
* [SUGGESTION] Replace `{}` with `unknown`.
* [SUGGESTION] Replace `{}` with `Record<string, never>`.
* [SUGGESTION] Replace `{}` with `NonNullable<unknown>`.
|
|
eslint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
eslint-v8-cache-key-state-Lint-161
Expired
|
43 Bytes |
|