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
Instead of building a crazy amount of API endpoints we could leverage GraphQL and appropriate resolvers to handle all the data fetching and manipulation from/to the frontend.
The text was updated successfully, but these errors were encountered:
Does this need to be focused on now? A REST API will do the job just as well and is much much simpler to develop for us now. This should be in "future plans". GraphQL is great, but it's overkill for this project, especially at this stage.
There's not really a clear upside of using GraphQL for our project, but multiple downsides - for example added complexity.
Does this need to be focused on now? A REST API will do the job just as well and is much much simpler to develop for us now. This should be in "future plans". GraphQL is great, but it's overkill for this project, especially at this stage.
There's not really a clear upside of using GraphQL for our project, but multiple downsides - for example added complexity.
I agree with this. As we mentioned before, this is an issue for future features and, while not currently being developed, is just here as a future flag.
Instead of building a crazy amount of API endpoints we could leverage GraphQL and appropriate resolvers to handle all the data fetching and manipulation from/to the frontend.
The text was updated successfully, but these errors were encountered: