New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from REST for GraphQL #217
Comments
We have the approach to discuss with the community and vote the features before open an issue for that. |
Thanks. My bad. Let me check it out |
Ideally, REST and GraphQL should both be implemented and available as plugins rather than being part of core. Let people chose what they want to (continue to) use rather dictating one or the other. |
@epakrat thanks for your input. You can actually make your voice heard by voting on these and other features via our https://petitions.classicpress.net/ website. |
Summarizing my comment at https://petitions.classicpress.net/posts/72/upgrade-rest-to-graphql: there is a |
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Feature request. This could be future/planned. REST API is currently bloated with so much information one seldom needs and could be improved in speed relatively. I suggest running with GraphlQL.
Expected Behavior
Possible Solution
This could be a start. https://github.com/wp-graphql/wp-graphql
The text was updated successfully, but these errors were encountered: