is the graphql support worth maintaining about use-http HOT 2 CLOSED

So I could be wrong here, but is the only reason they use client is because of versatility between frameworks? Such as react, vue, angular? From the client.js it looks like all the things they manage there could be done without a Client class which I think makes things simpler for the end user. I see this as a smaller, drop-in replacement for something like Apollo. I was also going to add documentation to show how this works just like Apollo and how it's basically a simpler tool to use

from use-http.

Also, I find the syntax to be nicer to read, because it makes the queries/mutations actionable. As in, it basically makes them into a JS function.

function QueryComponent() {
  const request = useQuery`
    query Todos($userID string!) {
      todos(userID: $userID) {
        id
        title
      }
    }
  `

  const getTodosForUser = id => request.query({ userID: id })

  return (
    <>
      <button onClick={() => getTodosForUser('theUsersID')}>Get User's Todos</button>
      {request.loading ? 'Loading...' : <pre>{request.data}</pre>}
    </>
  )
}

I'm open to discussing this though.

from use-http.