No I don't think you can consider GraphQL to be a kind of REST, since it doesn't follow the precepts of REST:
it doesn't use http verbs/methods in a semantic was
it doesn't supply different resources at different URLs
it doesn't use uniform interface for the URLs (i.e. that the path follows conventions like /users/:id)
it doesn't leverage (or even care about) media types (e.g. getting the same resource as JSON, XML, or something else entirely)
The only real overlap is that GraphQL typically uses http (though it doesn't really require that, conceptually) and a JSON-like syntax (just as actual JSON tends to be the preferred REST body syntax).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
No I don't think you can consider GraphQL to be a kind of REST, since it doesn't follow the precepts of REST:
The only real overlap is that GraphQL typically uses http (though it doesn't really require that, conceptually) and a JSON-like syntax (just as actual JSON tends to be the preferred REST body syntax).