Add test coverage for publications #614
TICS annotations
Annotations
github-actions / TICS annotations
Unsafe assignment of an error typed value.
Blocking
Level: 3, Category: Style
Line: 43, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe assignment of an error typed value.
Blocking
Level: 3, Category: Style
Line: 45, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe array destructuring of a tuple element with an error typed value.
Blocking
Level: 3, Category: Style
Line: 46, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe array destructuring of a tuple element with an error typed value.
Blocking
Level: 3, Category: Style
Line: 48, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe array destructuring of a tuple element with an error typed value.
Blocking
Level: 3, Category: Style
Line: 50, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe call of a(n) `error` type typed value.
Blocking
Level: 3, Category: Best Practices
Line: 52, TypeScript Coding Standard: no-unsafe-call
Avoid calling an any type value. The any type can sometimes leak into your codebase. The arguments to, and return value of calling an any typed variable are not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-call
github-actions / TICS annotations
Unsafe assignment of an error typed value.
Blocking
Level: 3, Category: Style
Line: 52, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe assignment of an error typed value.
Blocking
Level: 3, Category: Style
Line: 54, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe argument of type `any` assigned to a parameter of type `FormProps`.
Blocking
Level: 3, Category: Style
Line: 57, TypeScript Coding Standard: no-unsafe-argument
Avoid calling a function with any in its arguments, and it will disallow spreading any[]. the any type can sometimes leak into your codebase
Rule-help: https://typescript-eslint.io/rules/no-unsafe-argument
github-actions / TICS annotations
Unsafe call of a(n) `error` type typed value.
Blocking
Level: 3, Category: Best Practices
Line: 58, TypeScript Coding Standard: no-unsafe-call
Avoid calling an any type value. The any type can sometimes leak into your codebase. The arguments to, and return value of calling an any typed variable are not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-call
github-actions / TICS annotations
Unsafe call of a(n) `error` type typed value.
Blocking
Level: 3, Category: Best Practices
Line: 62, TypeScript Coding Standard: no-unsafe-call
Avoid calling an any type value. The any type can sometimes leak into your codebase. The arguments to, and return value of calling an any typed variable are not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-call
github-actions / TICS annotations
Unsafe member access .success on an `error` typed value.
Blocking
Level: 3, Category: Best Practices
Line: 62, TypeScript Coding Standard: no-unsafe-member-access
Avoid member access on any typed variables. The any type can sometimes leak into your codebase. Member access on any typed variables is not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-member-access
github-actions / TICS annotations
Unsafe member access .name on an `any` value.
Blocking
Level: 3, Category: Best Practices
Line: 64, TypeScript Coding Standard: no-unsafe-member-access
Avoid member access on any typed variables. The any type can sometimes leak into your codebase. Member access on any typed variables is not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-member-access
github-actions / TICS annotations
Invalid type "any" of template literal expression.
Blocking
Level: 3, Category: Functionality
Line: 64, TypeScript Coding Standard: restrict-template-expressions
Enforce template literal expressions to be of string type
Rule-help: https://typescript-eslint.io/rules/restrict-template-expressions
github-actions / TICS annotations
Unsafe call of a(n) `error` type typed value.
Blocking
Level: 3, Category: Best Practices
Line: 72, TypeScript Coding Standard: no-unsafe-call
Avoid calling an any type value. The any type can sometimes leak into your codebase. The arguments to, and return value of calling an any typed variable are not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-call
github-actions / TICS annotations
Unsafe member access .data on an `error` typed value.
Blocking
Level: 3, Category: Best Practices
Line: 72, TypeScript Coding Standard: no-unsafe-member-access
Avoid member access on any typed variables. The any type can sometimes leak into your codebase. Member access on any typed variables is not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-member-access
github-actions / TICS annotations
Unsafe return of a value of type error.
Blocking
Level: 3, Category: Best Practices
Line: 72, TypeScript Coding Standard: no-unsafe-return
Avoid returning any from a function. The any type can sometimes leak into your codebase. Returned any typed values not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-return
github-actions / TICS annotations
Unsafe assignment of an error typed value.
Blocking
Level: 3, Category: Style
Line: 72, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe call of a(n) `error` type typed value.
Blocking
Level: 3, Category: Best Practices
Line: 74, TypeScript Coding Standard: no-unsafe-call
Avoid calling an any type value. The any type can sometimes leak into your codebase. The arguments to, and return value of calling an any typed variable are not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-call
github-actions / TICS annotations
Unsafe assignment of an error typed value.
Blocking
Level: 3, Category: Style
Line: 74, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment
github-actions / TICS annotations
Unsafe call of a(n) `error` type typed value.
Blocking
Level: 3, Category: Best Practices
Line: 76, TypeScript Coding Standard: no-unsafe-call
Avoid calling an any type value. The any type can sometimes leak into your codebase. The arguments to, and return value of calling an any typed variable are not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-call
github-actions / TICS annotations
Unsafe member access .map on an `error` typed value.
Blocking
Level: 3, Category: Best Practices
Line: 76, TypeScript Coding Standard: no-unsafe-member-access
Avoid member access on any typed variables. The any type can sometimes leak into your codebase. Member access on any typed variables is not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-member-access
github-actions / TICS annotations
Unsafe return of a value of type error.
Blocking
Level: 3, Category: Best Practices
Line: 76, TypeScript Coding Standard: no-unsafe-return
Avoid returning any from a function. The any type can sometimes leak into your codebase. Returned any typed values not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-return
github-actions / TICS annotations
Unsafe member access .displayName on an `any` value.
Blocking
Level: 3, Category: Best Practices
Line: 77, TypeScript Coding Standard: no-unsafe-member-access
Avoid member access on any typed variables. The any type can sometimes leak into your codebase. Member access on any typed variables is not checked at all by TypeScript, so it creates a potential safety hole
Rule-help: https://typescript-eslint.io/rules/no-unsafe-member-access
github-actions / TICS annotations
Unsafe assignment of an `any` value.
Blocking
Level: 3, Category: Style
Line: 77, TypeScript Coding Standard: no-unsafe-assignment
Avoid assigning any to variables and properties
Rule-help: https://typescript-eslint.io/rules/no-unsafe-assignment