python-qlient VS vue-query

So I did what every programmer would do. I settled down in my basement, put every other project on hold and dove head over heels into a new project. The result? qlient. A "blazingly" fast and modern graphql client that was designed with simplicity in mind.

And so my qlient was born. resp. qlient-aiohttp for async but that's still WIP

If you're thinking of starting to use graphql with python, but just don't know how to get things going or which client library to use or whether to use a client library at all, then fear not and try the python qlient.

And that's when i decided to build qlient.

Python Qlient

I started using the Vue port of this recently, VueQuery. Once you understand that this replaces the need for a store (for data at least) then everything starts falling into place and its really easy to implement caching, infinite scrolling and other cool endpoint stuff.

I use vue-query and would recommend it.

For server-side state I find something like https://github.com/DamianOsipiuk/vue-query to be nicer than Vuex, and then you can reserve Vuex for purely client-side state

I think you are looking for https://github.com/DamianOsipiuk/vue-query It uses react-query/core under the hood.

Are you looking for this? https://github.com/DamianOsipiuk/vue-query

React-Query, SWR, Redux Toolkit Query, Vue Query for RESTful APIs

Check out swrv or vue-query, they do this for you. One or two people from the vuex core team work on swrv.

React Query is React specific, but its core was fully separated from React and it can be used to build solutions for other frameworks as well. Such solutions have already begun to emerge. For example, Vue Query.

Hey, might give https://vue-query.vercel.app/ a try soon