You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could look into adding a GraphQL endpoint. It would be entirely separate from this project just because of the nature of GraphQL, but it shouldn't be too difficult to get running.
could you elaborate what you mean by that, specifically?
Assuming the underlying object structure is detached enough from the actual api routes, it shouldn't be hard to integrate.
And, worst case you could simply wrap the REST api with GraphQL. (not as efficient as only querying exactly what is needed, but could still save some bandwidth)
Currently, meta is served entirely statically. Because the API is deterministic and REST API's are made entirely via the address, no computation is needed. All this project does is generate those static files that are served for queries.
What I'll likely end up doing is indeed wrapping the REST API with GraphQL. It shouldn't be hard to get setup, and the small amount of inefficiency isn't a huge concern given that all of the backend data is able to be accessed so quickly.
would it be possible to expose a GraphQL endpoint of the API, in addition to the current REST one?
The text was updated successfully, but these errors were encountered: