fix(deps): update dependency result-type-ts to v2.2.0 (#248) #404
bicstoneAnnotations
2 errors and 11 warnings
|
Build and Test
Error: Test Error
|
|
Build and Test
Error: Test Error
|
|
Build and Test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Build and Test:
src/common/stdout.spec.ts#L15
'process.stdout' will use Object's default stringification format ('[object Object]') when stringified
|
|
Build and Test:
src/common/stdout.spec.ts#L17
'process.stdout' will use Object's default stringification format ('[object Object]') when stringified
|
|
Build and Test:
src/main.ts#L33
Unexpected object value in conditional. The condition is always true
|
|
Build and Test:
src/main.ts#L33
Unnecessary conditional, value is always truthy
|
|
Build and Test:
src/main.ts#L48
Unexpected object value in conditional. The condition is always true
|
|
Build and Test:
src/main.ts#L48
Unnecessary conditional, value is always truthy
|
|
Build and Test:
src/main/getConfigs.ts#L133
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
|
|
Build and Test:
src/main/getConfigs.ts#L133
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
Build and Test:
src/main/getConfigs.ts#L133
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
|
|
Build and Test:
src/main/getConfigs.ts#L133
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|