Return detailed response #34
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
BREAKING CHANGE: The response body is no longer the 2nd callback argument, the detailed response is. The body is located under the `result` property. The `data` property is removed.
Codecov Report
@@ Coverage Diff @@
## release-candidate-v1 #34 +/- ##
========================================================
+ Coverage 93.35% 93.37% +0.01%
========================================================
Files 12 12
Lines 512 513 +1
Branches 151 151
========================================================
+ Hits 478 479 +1
Misses 33 33
Partials 1 1
Continue to review full report at Codecov.
|
dpopp07
added a commit
that referenced
this pull request
Aug 6, 2019
BREAKING CHANGE: The response body is no longer the 2nd callback argument, the detailed response is. The body is located under the `result` property. The `data` property is removed.
mkistler
pushed a commit
that referenced
this pull request
Sep 17, 2019
BREAKING CHANGE: The response body is no longer the 2nd callback argument, the detailed response is. The body is located under the `result` property. The `data` property is removed.
dpopp07
added a commit
that referenced
this pull request
Oct 3, 2019
BREAKING CHANGE: The response body is no longer the 2nd callback argument, the detailed response is. The body is located under the `result` property. The `data` property is removed.
dpopp07
added a commit
that referenced
this pull request
Oct 3, 2019
BREAKING CHANGE: The response body is no longer the 2nd callback argument, the detailed response is. The body is located under the `result` property. The `data` property is removed.
ibm-devx-automation
pushed a commit
that referenced
this pull request
Oct 3, 2019
# [1.0.0](v0.3.6...v1.0.0) (2019-10-03) ### Bug Fixes * Move check for serviceUrl to createRequest ([#47](#47)) ([6f04739](6f04739)) * parse result from response in token managers ([6bbe423](6bbe423)) * provide bundlers alternate file for browser support ([#58](#58)) ([88a9d16](88a9d16)) ### Build System * drop support for Node versions 6 and 8 ([#33](#33)) ([d47c737](d47c737)) ### Code Refactoring * look for credentials file in working dir before home dir ([#46](#46)) ([c5556de](c5556de)) * return detailed response as second callback argument ([#34](#34)) ([dc24154](dc24154)) ### Features * add `setServiceUrl` method as a setter for the `serviceUrl` property ([#41](#41)) ([cfb188f](cfb188f)) * add specific error handling for SSL errors with cloud private instances ([#54](#54)) ([056ec9a](056ec9a)) * export `UserOptions` interface from the BaseService ([#50](#50)) ([4f0075a](4f0075a)) * implement new authenticators to handle sdk authentication ([#37](#37)) ([f876b6d](f876b6d)) * refactor core to use Promises instead of callbacks ([#55](#55)) ([9ec8afd](9ec8afd)) ### BREAKING CHANGES * None of the authenticators or request methods take callbacks as arguments anymore - they return Promises instead. * Users that have credential files in both the working directory and the home directory will see a change in which one is used. * The internal property `url` no longer exists on the `baseOptions` object, it has been renamed to `serviceUrl` * The old style of passing credentials to the base service will no longer work. An Authenticator instance MUST be passed in to the base service constructor. * token managers no longer support user access tokens. use BearerTokenAuthenticator instead * The class names of the token managers have changed. * `Icp4dTokenManagerV1` renamed to `Cp4dTokenManager` * `IamTokenManagerV1` renamed to `IamTokenManager` * `JwtTokenManagerV1` renamed to `JwtTokenManager` * The public method `setAuthorizationInfo` is renamed to `setClientIdAndSecret` * The response body is no longer the 2nd callback argument, the detailed response is. The body is located under the `result` property. The `data` property is removed. * This SDK may no longer work with applications running on Node 6 or 8.
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.
Returns the "detailed response" (which includes the body, the headers, the status, etc.) as the first callback argument after error. This used to be the body itself, so this is a breaking change (pushing to the "next" branch).
Also, renaming the body property from
datatoresult. This is done to be consistent with the other SDKs.This will remove the need for the generated SDKs to use the
return_responseparameter to determine how to resolve Promises.Includes some test changes.