---
title: "Comment by Mikhail Molchanov on \"Become expert in React Query\" | Hashnode"
description: "Great article overall! However, I would not promote the idea of storing pure client state in RQ like you suggest in \"RQ as a state manage\" section. It's more li"
url: "https://hashnode.com/posts/become-expert-in-react-query/677ff7be1c567b36a9a3e77f/comment/678a31bcdec3bb4c0c81c3a2"
---

[Discussion](https://hashnode.com/posts/become-expert-in-react-query/677ff7be1c567b36a9a3e77f)

Comment [Become expert in React Query](https://hashnode.com/posts/become-expert-in-react-query/677ff7be1c567b36a9a3e77f)

[Mikhail Molchanov](https://hashnode.com/@mikhail-molchanov)

[Jan 17, 2025](https://hashnode.com/posts/become-expert-in-react-query/677ff7be1c567b36a9a3e77f/comment/678a31bcdec3bb4c0c81c3a2)

Great article overall! However, I would not promote the idea of storing pure client state in RQ like you suggest in "RQ as a state manage" section. It's more like a neat trick that you can use to make the RQ do what you want. Less experienced developers might take it as a strong advice and use it everywhere, which could easily turn into a mess.
