This repository has been archived by the owner on Aug 28, 2024. It is now read-only.
Update to support config of headers sent in requests (issue #125) #127
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.
What's in this Pull Request?
This PR contains an update to provide global configuration of the headers sent with each REST request. This resolves #125 by allowing a developer to set "application/json; odata=verbose" for the accept header as shown below:
This also enables the scenario of setting an authentication header using a previously retrieved bearer token - or any other headers that may be needed for a given solution. Currently "headers" is the only configurable property but we will add additional configuration options as they become required or found to provide some benefit.