fix(docs): rename Headers to HttpHeaders to avoid clash with DOM's Headers type #570
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 PR renames the client's
Headers
type toHttpHeaders
in order to avoid clashing with a built-in DOM Headers type.HttpHeaders
are also exported asHeaders
, so there is no backward-compatibility introduced herein.This change also fixes the model of the generated API documentation (created by api-extractor), the client's HttpHeaders now has a unique canonical name that is referenceable.
Checklist
yarn test
completes successfully