-
-
Notifications
You must be signed in to change notification settings - Fork 149
Replace rest with graphql for theme level support #360
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
Open
enmaboya
wants to merge
6
commits into
Kyon147:master
Choose a base branch
from
enmaboya:replace_rest_with_graphql_for_theme_level_support
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Replace rest with graphql for theme level support #360
enmaboya
wants to merge
6
commits into
Kyon147:master
from
enmaboya:replace_rest_with_graphql_for_theme_level_support
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VerifyScopes middleware + ApiHelper from Services is also using REST API for activateCharge, createCharge and createUsageCharge |
@enmaboya I am going to get this tested and deployed next week. |
Kyon147
previously approved these changes
Mar 25, 2025
@enmaboya can you just take a quick look at the conflicts and I will get this merged in to go with the next major release. |
ee894b2
to
917cb23
Compare
41dd5b5
to
f145bc2
Compare
@Kyon147 Conflicts resolved. |
@Kyon147 can you merge this ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The reason for switching from REST to GraphQL is the same as with access scopes. REST is deprecated. Additionally, REST is redundant; it retrieves too much data, making it roughly three times slower than GraphQL in this case. Moreover, I strongly doubt that the theme helper service was used by anyone or anywhere outside the package.