4 ms·
> ...they just happened to have a prebuilt UI component With respect, that's not what is described. OP rolled an API, handed documentation to frontend, and "af
by rendall 2y ago
> ...they just happened to have a prebuilt UI component
With respect, that's not what is described. OP rolled an API, handed documentation to frontend, and "after a week" frontend "came up" with a UI that held different expectations for how pagination works than the API actually worked. I'm being charitable in assuming that there was a good reason that this pagesize, offset pagination style could not work, but as written, there was no communication about that, neither to us the audience nor to OP's colleagues. In fact, frontend apparently expected this.
But why not discuss offset, pagination with colleagues? Why just present it as fait accompli and move on to create a library that further locks it in?
- alejo 2y agoMaybe this may help. What if we are not talking internal development teams but something different, like a commercial/public API? In those cases you cannot affort or expect to have meetings with folks to explian and communicate, and you also can appreciate more the abuse (unintended or not) that tokens can have. I particularly liked that OP mentioned about expiration, key rotation and more advanced features you can achieve with his proposal, like switching schemes
- rendall 2y agoAgreed: if the situation were completely and totally different to the one described by OP, then yes, different circumstances apply.