DEV Community

Discussion on: What new language/tool/etc. have you been meaning to learn but haven't gotten around to yet?

Collapse
mebble profile image
Neil Syiemlieh

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

Collapse
jacobmgevans profile image
Jacob Evans

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.

Collapse
kenbellows profile image
Ken Bellows

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!

Collapse
mebble profile image
Neil Syiemlieh

Awesome suggestion. I'll definitely try this out

Collapse
laurieontech profile image
Laurie

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).

Collapse
mebble profile image
Neil Syiemlieh

A Gatsby + GraphQL combo is exactly what I had in mind when thinking of learning graphQL :D

Collapse
tushark1 profile image
Tushar Khubani

I would personally suggest you to start with a crud project involving authentication and authorisation. Covers pretty much the basic necessities for a base.