Hi Adro! Even with fake data, these are still GraphQL resolvers. If you're looking to connect resolvers to a database, we cover that later in the series! I didn't include database concepts here because I wanted to explain fundamental concepts instead of spoon feeding a massive plate of database code. Thank you for the feedback though! I think I understand your perspective, but let me know if you have any requests or more constructive criticism.
@SingletonSean thx for taking it that way then. Do you happen to know resources or information how to connect it to a neo4j database ? (I already know that part) but having the hardest time fetching the relationships between the nodes
![⭐ฮิตในTikTok!! ( มะมะมะหมูเด้ง MooDeng ) Ver. แดนซ์ ReMix BY [ ดีเจกิต รีมิกซ์ ]](http://i.ytimg.com/vi/4noyAoMa7bQ/mqdefault.jpg)
Great lesson and very well organised!
I've subscribed. I'm looking forward to filtering and paging. I've read the docs, but you do a better job of explaining the things.
That's great to hear Dan, welcome! I've actually already started putting together videos for filtering/paging/sorting/etc, so stay tuned
Just write acronyms like any other word in the names. i mean do not make all letters upper case beacause it is an acronym. It solves many problems.
Wow great,, thanks!
nice, have you try implementing the authorization and getting the current user login?
Thanks Norman, and yes! We will be covering authentication and authorization later in this series
👍
Your videos' auto-generated captions sometimes French, sometimes Vietnamese. Can you specify the language for the video?
yeah. I have experienced the same problem
do not name entity models with "type" in the end because later u will need to create entity which is type of some another, and that would be a problem
Yeah. It was confusing for me.
bogus is 63 million now :)
70.3 million
Looks Spoon feeding to me. And the part were you generate fake data is hilarious and then call that resolvers haha
Hi Adro! Even with fake data, these are still GraphQL resolvers. If you're looking to connect resolvers to a database, we cover that later in the series! I didn't include database concepts here because I wanted to explain fundamental concepts instead of spoon feeding a massive plate of database code.
Thank you for the feedback though! I think I understand your perspective, but let me know if you have any requests or more constructive criticism.
@SingletonSean thx for taking it that way then. Do you happen to know resources or information how to connect it to a neo4j database ? (I already know that part) but having the hardest time fetching the relationships between the nodes