Did we consider making pagination optional (at least temporarily to avoid increasing major version all the time)?
Let's say we call:
/api/geographicZones
And we get a response like this:
[ { zone }, { zone }, ... ]
But, when we call:
/api/geographicZones?page=2 (or whatever pagination parameter)
Only then we get a response wrapped in pagination object.
Guess that might require some more effort on backend, but I guess we'd avoid backwards compatibility issues.
Best,
Paweł