through doing so, it is understandable from first perspective why & how graphQL is the layer between database.
One can do specific endpoint validating conditional logic with HTTP requests to achieve same result.
Just as one can run such validating conditions against (typeof my_var) in javascript to achieve same end purpose of typescript.
bookmarking a thought as a somewhat novice somewhat proficient in typescript.
let my_shirt:string = "blue shirt";
to go from simple such declarations in typescript,
to using a type safe global store that uses a type interface, explicitly defined default values, and exportable wrapper.
Typescript can get very "locked down" in regards to the values it will safely parse for certain variables.
GraphQL seems in line with things moving towards typescript and in specifying format for variables, API, values, keys etc.
through doing so, it is understandable from first perspective why & how graphQL is the layer between database.
One can do specific endpoint validating conditional logic with HTTP requests to achieve same result. Just as one can run such validating conditions against (typeof my_var) in javascript to achieve same end purpose of typescript.
bookmarking a thought as a somewhat novice somewhat proficient in typescript.
let my_shirt:string = "blue shirt"; to go from simple such declarations in typescript,
to using a type safe global store that uses a type interface, explicitly defined default values, and exportable wrapper.
Typescript can get very "locked down" in regards to the values it will safely parse for certain variables. GraphQL seems in line with things moving towards typescript and in specifying format for variables, API, values, keys etc.
[5:05pm]