Created by: f-f
PR checklist
-
Read the contribution guidelines. -
Ran the shell script under ./bin/
to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh
and./bin/security/{LANG}-petstore.sh
if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\
. -
Filed the PR against the correct branch: Default: master
. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
Description of the PR
Before the change, to update the api-context (e.g. the URL of the API) it was necessary to wrap all the calls in (with-api-context new-context api-call-here)
.
Since in some cases the new context needs to be shared globally in the app (e.g. we have a different URL for services in dev/test/production), it is useful to have a method to change the api-context
once and for all.
Example usage:
(set-api-context {:base-url "https://new-url-here"})
/cc @wing328