I am also in the middle of moving off graphql to REST api. It is a 5 years old project and the graphql part was implemented with a very old spec. Since it has not been well maintained, it could not catch up with any features offered by graphql and users need to write their own queries by hand due to spec compatibility.
Rewriting it to REST allows us to "rebrand" these apis. At least, it does not scare our api users as the word "graphql" did.
Rewriting it to REST allows us to "rebrand" these apis. At least, it does not scare our api users as the word "graphql" did.