Im think creating custom solutions for everything is not good idea and this would solve most of the issues with the api calls we face now or will face in the future with less effort and more efficiency...
So the biggest thing is consistency so we have one standardised way of doing queries
Also there are some nice caching options that we can use throughout the codebase so that we don't refetch data unnecessarily
Some of the ways this can be useful: 1) Standardised state management: So we don't have to repeat the same logic on all api's we do it does it out of the box 2) Parallel queries: I think this one will speed things up for fetching ens data for domains and also for fetching bulk data for poap themes https://tanstack.com/query/v4/docs/guides/parallel-queries 3) Pagination/Infinite Scroll: Also very useful for pagination or infinite scroll as it handles alot of the stuff we won't need to https://tanstack.com/query/v4/docs/guides/paginated-queries , https://tanstack.com/query/v4/docs/guides/infinite-queries 4) Dependent queries There are couple of places where this can be used as well https://tanstack.com/query/v4/docs/guides/dependent-queries 4) Cleaner code
Im think creating custom solutions for everything is not good idea and this would solve most of the issues with the api calls we face now or will face in the future with less effort and more efficiency...
So the biggest thing is consistency so we have one standardised way of doing queries
Also there are some nice caching options that we can use throughout the codebase so that we don't refetch data unnecessarily
[x] useEnsMetadata
[x] depoyedNimiPage
[x] generatedEnsData
[x] GraphQlRequests
[ ] PublishNimi
[x] Twitter import
[ ] Upload nimi assets
[x] Linktree import
[x] poap fetching