GraphQL. The hype makes me wanna join in, but I just don't feel like I need it yet. I guess I just haven't worked on any project large enough to warrant it
You could try creating a standalone GraphQL API instead of a RESTful one. One of the jobs I did the only thing Express was doing was running Apollo server, everything else was pure GraphQL API.
Full-time web dev; JS lover since 2002; CSS fanatic. #CSSIsAwesome
I try to stay up with new web platform features. Web feature you don't understand? Tell me! I'll write an article!
He/him
A fun experiment to try it out is to find a public REST API, ideally something that can be modeled with some sort of type system (my recommendation: the PokéAPI), run some queries to get familiar with it, then build a GraphQL layer in front of it. Gets you familiarized with GraphQL types and resolvers and such. There's a slight learning curve at the beginning, but it's not bad, and it's a very nice interface to query once it's set up!
Software dev at Netflix | DC techie | Conference speaker | egghead Instructor | TC39 Educators Committee | Girls Who Code Facilitator | Board game geek | @laurieontech on twitter
If you want a really clean way to play around with GraphQL make a Gatsby project and throw in some kind of static content.
When you spin up the project for development it generates an additional localhost endpoint that consists of a stand alone GraphQL playground (think postman for REST).
I would personally suggest you to start with a crud project involving authentication and authorisation. Covers pretty much the basic necessities for a base.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
GraphQL. The hype makes me wanna join in, but I just don't feel like I need it yet. I guess I just haven't worked on any project large enough to warrant it
You could try creating a standalone GraphQL API instead of a RESTful one. One of the jobs I did the only thing Express was doing was running Apollo server, everything else was pure GraphQL API.
A fun experiment to try it out is to find a public REST API, ideally something that can be modeled with some sort of type system (my recommendation: the PokéAPI), run some queries to get familiar with it, then build a GraphQL layer in front of it. Gets you familiarized with GraphQL types and resolvers and such. There's a slight learning curve at the beginning, but it's not bad, and it's a very nice interface to query once it's set up!
Awesome suggestion. I'll definitely try this out
If you want a really clean way to play around with GraphQL make a Gatsby project and throw in some kind of static content.
When you spin up the project for development it generates an additional localhost endpoint that consists of a stand alone GraphQL playground (think postman for REST).
A Gatsby + GraphQL combo is exactly what I had in mind when thinking of learning graphQL :D
I would personally suggest you to start with a crud project involving authentication and authorisation. Covers pretty much the basic necessities for a base.