@wraptile @bhaugen i think all the graphql apis i've been working with so far were totally friendly (say, github). Also, in terms of developer-consumer friendliness, IMO even the worst graphql implementation is nicer to work with than the Best rest api (given they both share exact the same amount of data). Especially that graphql auto-suggests fields and self-documents itself. But, if the implementation is bad, its not really graphqls fault
Conversation
Notices
-
Prismo △ (prismo@mastodon.social)'s status on Saturday, 04-May-2019 09:41:39 UTC Prismo △ -
Prismo △ (prismo@mastodon.social)'s status on Saturday, 04-May-2019 09:43:56 UTC Prismo △ @wraptile @bhaugen also, you totally can use graphql endpoint with curl. Its not gonna be easy for More complex queries but you totally can do that.
Ps. Graphql is never gonna be an official go-to api of prismo. Its gonna be a secondary one at most. I decided to try the C2S route as a primary one
-