Replace rest with graphql for theme level support #360
Conversation
This file contains 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. |
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.