Flexibility features #2
Open
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
to give the end-user better control over calling their REST APIs in case they don't follow the standard CRUD model. This allows for calls like base_url+'/some_string_or_different_format/or_different_path_entirely'. Added a feature to allow striping the trailing '/' from the API url if desired. Added a feature to allow passing custom HEADERS with the API calls. Modified, base functions to also allow passing a JSON body to an api call instead of just parameters, as some APIs take strictly JSON.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I added some features that allow you to POST/PUT json directly to APIs, as well as modify the URLs via patterns in your models.
This is helpful for:
I also added the ability to pass custom headers and optionally remove the trailing '/' from REST urls as some legacy APIs didn't route correctly with a trailing '/'