Skip to content

Add support for cursor based pagination and remove page based pagination #75

Add support for cursor based pagination and remove page based pagination

Add support for cursor based pagination and remove page based pagination #75

Triggered via pull request August 25, 2023 16:41
Status Failure
Total duration 43s
Artifacts

test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

32 errors and 9 warnings
linter: chartmogul.go#L170
`compatability` is a misspelling of `compatibility` (misspell)
linter: integration_tests/customers_test.go#L84
`validateListCustomers` - `customers` is unused (unparam)
linter: integration_tests/customers_test.go#L103
`validateSearchCustomers` - `dsUUID` is unused (unparam)
linter: integration_tests/invoices.go#L12
`createTestInvoicesForcustomer` - `dsUUID` is unused (unparam)
linter: integration_tests/invoices_test.go#L66
`validateListInvoices` - `dsUUID` is unused (unparam)
linter: integration_tests/plans_test.go#L85
`validateListPlans` - `plans` is unused (unparam)
linter: integration_tests/invoices.go#L41
mnd: Magic number: 3, in <argument> detected (gomnd)
linter: integration_tests/invoices.go#L74
mnd: Magic number: 3, in <argument> detected (gomnd)
linter: integration_tests/invoices.go#L23
mnd: Magic number: 4500, in <assign> detected (gomnd)
linter: integration_tests/invoices.go#L25
mnd: Magic number: 2, in <assign> detected (gomnd)
test (1.13): integration_tests/customers_subscriptions_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.13): integration_tests/customers_test.go#L24
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.13): integration_tests/invoices_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.13): integration_tests/plans_test.go#L24
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.13): integration_tests/subscription_events_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.13): integration_tests/subscriptions_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.13)
Process completed with exit code 2.
test (1.17)
The job was canceled because "_1_13" failed.
test (1.12): integration_tests/customers_subscriptions_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.12): integration_tests/customers_test.go#L24
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.12): integration_tests/invoices_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.12): integration_tests/plans_test.go#L24
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.12): integration_tests/subscription_events_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.12): integration_tests/subscriptions_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.12)
The operation was canceled.
test (1.11): integration_tests/customers_subscriptions_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.11): integration_tests/customers_test.go#L24
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.11): integration_tests/invoices_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.11): integration_tests/plans_test.go#L24
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.11): integration_tests/subscription_events_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.11): integration_tests/subscriptions_test.go#L23
t.Cleanup undefined (type *testing.T has no field or method Cleanup)
test (1.11)
The operation was canceled.
test (1.19)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.14)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.16)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.18)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.13)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
code-coverage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.12)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/