I do not agree with removing graphql from our documentation. This is our API, if anything, it would be nice to have the API schema autogenerated and published. There are no usability issues with Graphql that we observed from interacting with customers. Yes, more people are familiar with rest than graphql, but no one has issues learning it and using it effectively.
I do not agree with removing graphql from our documentation. This is our API, if anything, it would be nice to have the API schema autogenerated and published. There are no usability issues with Graphql that we observed from interacting with customers. Yes, more people are familiar with rest than graphql, but no one has issues learning it and using it effectively.