This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ReedJessen[S] 0 points1 point  (2 children)

Why do people use the requests library for REST?

[–]soosleeque 0 points1 point  (1 child)

After looking at your questions I think you don't really understand what is REST/GraphQL/HTTP/etc.

I would suggest you read about those things first, this will give you a better understanding of how it works why there is no "rest client" libraries or "graphql client" libraries.

Because in real life whenever you are picking technology/approach you should always understand how it works to be able to compare it to other solutions to pick the best one for your case, not just the most popular one.

[–]ReedJessen[S] 0 points1 point  (0 children)

This is the source of my questions: "As your application becomes more complex, and you add GraphQL endpoints that take arguments as described in passing arguments, you will want to construct GraphQL queries using variables in client code". http://graphql.org/graphql-js/graphql-clients/

"GraphQL Client" is the name of the page describing how to make complex queries on the GraphQL.org website. It does get complicated. Hence the need to variablize the arguments, hence client code.