Honest question: why would you have cared for a GraphQL endpoint if the REST API contains what you need (I'm talking about content, not form, let's assume the new REST API is already satisfactory in its content) ?
It's not necessarily that it's not a GraphQL API, it's that they seemed to have explored it for a long time at least to my knowledge, but then release an adaptation of REST to the public
Kinda disappointed they didn't actually make it a graphql endpoint, I thought that was the plan
I totally agree
Honest question: why would you have cared for a GraphQL endpoint if the REST API contains what you need (I'm talking about content, not form, let's assume the new REST API is already satisfactory in its content) ?
It's not necessarily that it's not a GraphQL API, it's that they seemed to have explored it for a long time at least to my knowledge, but then release an adaptation of REST to the public
Don't know if they use it internally
Sure, that could be.
I was curious about your preference over having an external GraphQL API over a REST one moreso than their internal architecture.
After all, unless they tell us, we won't know if internally they use GraphQL or RPC or whatever to have microservices communicate