Is this really a problem we need to solve with technology? I've never seen this happen in the real world. But by the motivation presented in the repo as well a

Is this really a problem we need to solve with technology? I've never seen this happen in the real world. But by the motivation presented in the repo as well as some commentaries in this thread I got the impression this is a miscommunication issue. I my experience most mid-level engineers are fully aware about the differences between "pagination token" and "page/size" based pagination strategies. So when this kind of situation happens I get the impression that both teams were never in the same page. Maybe someone wrote "the api needs to have pagination" in a design doc and nobody bothered to ask for the details. To make things worse this problems only appear when we start to make some e2e tests, but by that point the deadline is generally pretty close. And this creates a big incentive for people to get creative in order to deliver on time.