error:
not really an error but, learning GraphQLHTTP specifically for an interview, leaves the decision in uncertainty.
what chat has to say about GQL Correspondent to this app's version of next: "next": "13.4.9",
proposed approach:
using GraphQLExpress (terminal was saying deprecated, w/ that same library now understood to be GraphQLHttp ( i think )
GQLexpress deals with the queries and mutations but that doesn't mean graphql-request is correct, (it does sound to be)
// also... this isn't a crazy complicated app, saw something on google saying: GraphQL on a small app can overcomplicate it.
I think using the "focused on ease of use and http requests" is perfect for an app that could do well with GQL but doesn't need all the extra features.
bookmark: in react/express GraphQL can and did go successfully in my situation in server/index.js
was going to wonder where it would go and think pages/api but could be wrong
[2:17am]
attempting to do: set up GraphQL for next.
error: not really an error but, learning GraphQLHTTP specifically for an interview, leaves the decision in uncertainty.
what chat has to say about GQL Correspondent to this app's version of next: "next": "13.4.9",![Screen Shot 2023-07-07 at 2 07 02 AM](https://github.com/frankcollins3/Next-Water-App/assets/73137934/1299035b-587a-4109-b73e-aa167cd94d6f)
proposed approach: using GraphQLExpress (terminal was saying deprecated, w/ that same library now understood to be GraphQLHttp ( i think ) GQLexpress deals with the queries and mutations but that doesn't mean graphql-request is correct, (it does sound to be)
// also... this isn't a crazy complicated app, saw something on google saying: GraphQL on a small app can overcomplicate it. I think using the "focused on ease of use and http requests" is perfect for an app that could do well with GQL but doesn't need all the extra features.