Use params schemas for all methods #57
gmethvinAnnotations
32 errors and 3 warnings
|
Test (Node 20):
tests/integration/catalogs.test.ts#L261
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 20):
tests/integration/catalogs.test.ts#L215
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 20):
tests/integration/catalogs.test.ts#L202
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 20):
tests/integration/catalogs.test.ts#L199
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 20):
tests/integration/catalogs.test.ts#L131
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 20):
tests/integration/catalogs.test.ts#L80
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 20):
tests/integration/catalogs.test.ts#L45
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 20):
tests/integration/catalogs.test.ts#L28
Expected 1 arguments, but got 2.
|
|
Test (Node 20):
tests/integration/campaigns.test.ts#L172
Argument of type 'number[]' is not assignable to parameter of type '{ ids: number[]; }'.
|
|
Test (Node 20):
tests/integration/campaigns.test.ts#L164
Argument of type 'number' is not assignable to parameter of type '{ listId: number; }'.
|
|
Test (Node 22)
The strategy configuration was canceled because "test._20" failed
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L261
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L215
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L202
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L199
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L131
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L80
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L45
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 22):
tests/integration/catalogs.test.ts#L28
Expected 1 arguments, but got 2.
|
|
Test (Node 22):
tests/integration/campaigns.test.ts#L172
Argument of type 'number[]' is not assignable to parameter of type '{ ids: number[]; }'.
|
|
Test (Node 22):
tests/integration/campaigns.test.ts#L164
Argument of type 'number' is not assignable to parameter of type '{ listId: number; }'.
|
|
Test (Node 18)
The strategy configuration was canceled because "test._20" failed
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L261
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L215
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L202
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L199
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L131
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L80
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L45
Argument of type 'string' is not assignable to parameter of type '{ catalogName: string; }'.
|
|
Test (Node 18):
tests/integration/catalogs.test.ts#L28
Expected 1 arguments, but got 2.
|
|
Test (Node 18):
tests/integration/campaigns.test.ts#L172
Argument of type 'number[]' is not assignable to parameter of type '{ ids: number[]; }'.
|
|
Test (Node 18):
tests/integration/campaigns.test.ts#L164
Argument of type 'number' is not assignable to parameter of type '{ listId: number; }'.
|
|
Test (Node 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test (Node 18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|