Hi Amy,

Thanks for the feedback, I really appreciate it, and I really wanted to do more or less what you explain.

The problem is that in fact I do not have too much experience with RTK (in fact the code that you see in the article is the first time that I have been using it).

I tried a little bit RTK, but I did not use it because 1) I did not get a clear picture from the documentation, neither from the examples, and 2) I have to try several approaches to learn how to write tests to force me to use RTK without great implementation leaps.

About if RTK has tests or not, it is not a concern for me. I do not know how to express it well, but I hope them to have it, because I can rely that future releases would break almost nothing), but, beyond that point, they do not influence what I test. Because I test business rules, not code, so I if a tool is tested or not, it is collateral, all that I want is to test if the code satisfies the business rules. So, the tests that I have, and what they test, would not change.

(Although that the implementation details might)

This series of articles (that are really costly to write for me, I often spend a couple of days), try to guide someone in the philosophy of doing the smallest changes possible. Which is really hard. I am not concern about exact tools, but more about strategies of how to split development in several really split steps. And that is what I want to teach. That is also why I decided to continue with the article, although not knowing well RTK. Also, I have to confess, that the other reason is that being at closer to the basics, helps to do the same steps with other frameworks or environments.

All that said, if you write an article about how to use RTK Query, I would love to read it, and finally learn how to use it.

Thank you so much for your sincere feedback!

David