So glad to see the content resonating with others! More apollo content to come, working on full projects with apollo / react so hopefully those will be helpful!
been looking for a great break down of resolvers for a few days now, this is by far the best. Curious tho, a resolver for each and every type/query seems very antithetical to DRY practices. Could you not just have 1 resolver that resolves based on the query parameters? Or is their segmentation more beneficial in the sense of separating concerns?
Great video, not sure why I didn't see this before on your channel. I noticed you mentioned going over resolver chains but you didn't cover it, is that in a different video?
Glad I found your channel. Much potential! I hope you have more apollo react content coming.
So glad to see the content resonating with others! More apollo content to come, working on full projects with apollo / react so hopefully those will be helpful!
been looking for a great break down of resolvers for a few days now, this is by far the best. Curious tho, a resolver for each and every type/query seems very antithetical to DRY practices. Could you not just have 1 resolver that resolves based on the query parameters? Or is their segmentation more beneficial in the sense of separating concerns?
Great video, not sure why I didn't see this before on your channel. I noticed you mentioned going over resolver chains but you didn't cover it, is that in a different video?
Great introduction. Thank you. What about when you want to combine multiple data sources?
Im glad i found it.. please make a video about context.. passing token/user to resolvers :)
9:05 that backticks making my code orange like " " and its not working, what should i do?
Thankuuu 🔥
Nice video! Question… i realize it’s just a name but why name a query with a verb that sounds like a mutation? That’s confusing.
That is confusing, my bad. I’ll make an effort to avoid similar confusions in future tutorials. Thanks for the comment
Thx 🎉❤
Got you :) thanks for watching