commit to illustrate changes for custom-http-client (do not merge) #407
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.
This example illustrates the feature-request in #400
The library-user can specify a custom function that sends requests to the backend (as illustrated in
test/e2e/v3.custom.spec.js
Helper functions like "getToken" and "getUrl" are not provided and must be written by the library-user.
The downside is that
ApiResult
andApiRequestOptions
would become part of the official API, which will impose restrictions in SemVer-versioning. I can understand if you don't want that.Final polishing and tests are still missing. Before I go any further I would like to hear your opinion.