docs: document supported content encodings - #463
Open
asllanmaciel wants to merge 1 commit into
Open
asllanmaciel wants to merge 1 commit into
asllanmaciel wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Addresses the discoverability part of #381.
ContentEncodingis now a public backed enum, so applications can derive the library-supported values withContentEncoding::cases()instead of duplicating a private/hard-coded list. This updates the README to show that approach and clarifies that a selectedcontentEncodingshould be supported by both the browser and this library.The automatic-negotiation API proposed in #381 remains a separate design choice; this PR only documents the capability that exists today.
Validation:
git diff --check[aesgcm,aes128gcm]Docs-only change; no production code changed.