GET /api/v2/ticket_fields may require cursor pagination, which TicketClient#listTicketFields() is not setup to handle.
Tests need validate this will work when a znedesk instance has more than 100 fields in a response
Proposed solution
Include it in testing
A test validates that a one locale has less than 100 tickets, and another has more than 100 tickets. If one doesn't have sufficient ticket fields, then the test adds a bunch. if both locales have more than 100, then the user will need to remedy the sandbox or provide a new sandbox with this setup.
Problem with this is that setting it up via a test may make that first run of the test kinda flaky, depending on how long it takes for zendesk's GET /api/v2/ticket_fields to return the updated information
provide a setup script
In the contributing doc there's a bunch of info on what the sandbox needs to have in terms of fields and whatnot. We could include a script of some sort to make sure there are enough custom field types.
GET /api/v2/ticket_fields may require cursor pagination, which TicketClient#listTicketFields() is not setup to handle.
Tests need validate this will work when a znedesk instance has more than 100 fields in a response
Proposed solution
Include it in testing
A test validates that a one locale has less than 100 tickets, and another has more than 100 tickets. If one doesn't have sufficient ticket fields, then the test adds a bunch. if both locales have more than 100, then the user will need to remedy the sandbox or provide a new sandbox with this setup.
Problem with this is that setting it up via a test may make that first run of the test kinda flaky, depending on how long it takes for zendesk's GET /api/v2/ticket_fields to return the updated information
provide a setup script
In the contributing doc there's a bunch of info on what the sandbox needs to have in terms of fields and whatnot. We could include a script of some sort to make sure there are enough custom field types.