Overview
Now that we've got the course, section, professor resolver all set up. Implement the field resolver from section to course, and section to professor, AND the data-loader to optimize the N+1 query problems.
Here are a few resources I'd recommend you take a look at, as implementing dataloader is probably the most difficult thing for graphql, let alone implementing it in Go:
Repo for API workshop
Stack Overflow
Our docs
gqlgen docs
The reason I put gqlgen docs at the bottom is because it's not really well-documented, and also because it uses SQL database as examples, so it'd be relatively hard to map it to NoSQL like Mongo. Nevertheless, it's still good source to get a grasp of theory.
Also be aware of the possibility that you might need configure some sort of middleware when you work on this.
Overview
Now that we've got the course, section, professor resolver all set up. Implement the field resolver from section to course, and section to professor, AND the data-loader to optimize the N+1 query problems.
Here are a few resources I'd recommend you take a look at, as implementing dataloader is probably the most difficult thing for graphql, let alone implementing it in Go:
Repo for API workshop
Stack Overflow
Our docs
gqlgen docs
The reason I put gqlgen docs at the bottom is because it's not really well-documented, and also because it uses SQL database as examples, so it'd be relatively hard to map it to NoSQL like Mongo. Nevertheless, it's still good source to get a grasp of theory.
Also be aware of the possibility that you might need configure some sort of middleware when you work on this.