Skip to content
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

Closed
bahiirwa opened this issue Sep 24, 2018 · 5 comments
Closed

Upgrade from REST for GraphQL #217

bahiirwa opened this issue Sep 24, 2018 · 5 comments

Comments

@bahiirwa
Copy link
Contributor

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

  • Improved speed on API.
  • Query only information needed by user.

Possible Solution

This could be a start. https://github.com/wp-graphql/wp-graphql

@Mte90
Copy link
Contributor

Mte90 commented Sep 24, 2018

We have the approach to discuss with the community and vote the features before open an issue for that.
Check https://petitions.classicpress.net/ to follow our workflow :-)

@Mte90 Mte90 closed this as completed Sep 24, 2018
@bahiirwa
Copy link
Contributor Author

Thanks. My bad. Let me check it out

@epakrat
Copy link

epakrat commented Sep 26, 2018

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.

@senlin
Copy link
Contributor

senlin commented Sep 26, 2018

@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.

@nylen
Copy link
Contributor

nylen commented Oct 1, 2018

Summarizing my comment at https://petitions.classicpress.net/posts/72/upgrade-rest-to-graphql: there is a _fields parameter which satisfies the original need for this issue, and we are probably about 3 years too late to decide not to include the REST API.

mattyrob referenced this issue in ClassicPress/ClassicPress Nov 20, 2023
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@viktorix viktorix transferred this issue from ClassicPress/ClassicPress Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants