Breaking React Query's API on purpose
Read OriginalThis article discusses the deliberate decision to break React Query's API in version 5 by removing onSuccess, onError, and onSettled callbacks from useQuery. It explores the challenges of API design, the philosophy behind major version bumps in software libraries, and why certain features are removed despite user backlash. The author explains the drawbacks of these callbacks and distinguishes this change from useMutation callbacks.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
Introducing GPT-5.1 for developers
Simon Willison
•
6 votes
2
🧠 Build an Agent Chat that Remembers — Persisting Conversations with Microsoft Agent Framework
Bruno Capuano
•
3 votes
3
Using A Hidden Submit Button To Ensure Unnamed Submissions
Ben Nadel
•
3 votes
4
uv+just for testing multiple Python versions
Daniel Feldroy
•
3 votes
5
ServiceNow and Microsoft Copilot
Marius Sandbu
•
2 votes
6
Cursor 2.0 and Composer Model
Codeaholicguy
•
2 votes
7
Agentic AI and Security
Martin Fowler
•
2 votes
8
Springs and Bounces in Native CSS
Josh Comeau
•
2 votes
9
Importing vs fetching JSON
Jake Archibald
•
2 votes
10
llm-anthropic 0.22
Simon Willison
•
1 votes