What's the API breaking change that cost you the most time to fix?
by•
One we found this week in a user's repo: a provider answered HTTP 200 with the error buried in the body once you paged too far. Nothing failed, the app just had fewer results than it thought. Curious what yours was and how long it took to find.

6 views

Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.