Adding support for REST resources #139
Merged
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
paulomarg
force-pushed
the
paulo/add_rest_wrapper_support
branch
2 times, most recently
from
54fe39d to
05ed892
Compare
paulomarg
force-pushed
the
paulo/add_rest_wrapper_support
branch
from
05ed892 to
38731d1
Compare
mllemango
approved these changes
Feb 28, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
WHY are these changes introduced?
We want to support creating classes that encapsulate the Admin API's REST resources, to make it easier for apps to interact with that API in an OO way.
WHAT is this pull request doing?
Creating a "base" REST resource which provides all of the functionality classes would need to be able to map API calls to specific objects.
Type of change
Checklist