This repository has been archived by the owner on Apr 11, 2024. It is now read-only.
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.
WHY are these changes introduced?
Currently, we can't handle requests like access scopes (
/admin/oauth/access_scopes.json
) or token access (/admin/api_permissions/current.json
), because these resources use custom paths instead of the default/admin/api/{version}/...
.This means we can't easily reach those endpoints unless the code uses the base HTTP client that the REST one is built upon, which makes things unnecessarily complicated.
WHAT is this pull request doing?
This PR solves that problem by allowing REST calls in the Admin API client to be made using a full path. Therefore, requests like
work just like any regular request would.
Type of change
Checklist