but Iām having issues with a lot of requests being...
# prisma-whats-newa
albinekb
10/07/2017, 2:00 PMbut Iām having issues with a lot of requests being sent
h
huv1k
10/07/2017, 2:17 PMYou can use http://dev.apollodata.com/core/network.html#query-batching š
a
albinekb
10/07/2017, 2:29 PMBut what is the recommended way to do it?
albinekb
10/07/2017, 2:30 PMhaving a lot of
graphqlh
huv1k
10/07/2017, 2:32 PMdepends on size of application i think
huv1k
10/07/2017, 2:32 PMif you have many components its better idea to couple graphql with each component
r
rein
10/07/2017, 2:34 PMbut am I correct in assuming that if you fetch a post that is already in the cache, it will not call the server?
h
huv1k
10/07/2017, 2:35 PMdepends of query setings you can force to refetch
r
rein
10/07/2017, 2:38 PMno no, I dont want that š I prefer to use the cache. But apollo is smart enough for that I take it
f
florian
10/07/2017, 2:40 PMFrom my still very small experience with Apollo caching is default behavior, you have to explicitly tell it to not cache
florian
10/07/2017, 2:40 PM@huv1k thanks for sharing the batching its pretty awesome
h
huv1k
10/07/2017, 2:41 PMyea, but if you for example mutate query, you can change it in cache
r
rein
10/07/2017, 2:42 PMgot it
rein
10/07/2017, 2:42 PMthanks š
h
huv1k
10/07/2017, 2:42 PMbut i am not expert š
huv1k
10/07/2017, 2:42 PMeverything is from my observations i made
r
rein
10/07/2017, 2:42 PMbut there is no performance penalty when wrapping multiple components in HOCs right?
h
huv1k
10/07/2017, 2:43 PMthere is always š
huv1k
10/07/2017, 2:43 PMmore code to execute
r
rein
10/07/2017, 2:43 PMright, so what do you do? pass props or wrap components in hocs?
h
huv1k
10/07/2017, 2:44 PMi wrap components because of readability code
huv1k
10/07/2017, 2:45 PMbut i am not right person to ask about stuff like this, i dont have enought experiences with big projects š
huv1k
10/07/2017, 2:45 PMor complicated applications š
f
florian
10/07/2017, 2:46 PMOn the app I'm building the pattern we adopted is we have view components (that match a react-router url) that are wrapped and pass down data via props to its child
florian
10/07/2017, 2:47 PMThe few exception being a notification widget that is living in it's own word
florian
10/07/2017, 2:47 PMas well as a messenger like thingy that works independently with subscriptions
r
rein
10/07/2017, 2:48 PMwhat about stuff like currentUser? A lot of components need that info right?
h
huv1k
10/07/2017, 2:49 PMdepends on your application š
r
rein
10/07/2017, 2:49 PMso there is no best practice in the community?
f
florian
10/07/2017, 2:50 PMcurrentUser is hooked to most of our view components
florian
10/07/2017, 2:51 PMActually we are thinking having it hooked to the main App and passed to the views as props
r
rein
10/07/2017, 2:52 PMso to each prop youd pass currentUser then?
rein
10/07/2017, 2:52 PMinteresting
rein
10/07/2017, 2:52 PMim having a lot of props being passed everywhere and it gets a bit convoluted
f
florian
10/07/2017, 2:53 PMI guess the best practice is when you find yourself in this situation you should refactor š
florian
10/07/2017, 2:57 PMBut if performance is your worry I think the best is to first track re renders when testing your app
florian
10/07/2017, 2:59 PMYou can read more about this here https://marmelab.com/blog/2017/02/06/react-is-slow-react-is-fast.html
r
rein
10/07/2017, 3:00 PMits not really my worry, Im just not really experienced
rein
10/07/2017, 3:00 PMI would like to adhere to best practices
rein
10/07/2017, 3:00 PMso thats why I asked
rein
10/07/2017, 3:00 PMits not that im suffering from bad performance or huge rerenders at the moment