docs: explain *-base features and document the full feature flag set#750
Merged
Conversation
kylebarron
approved these changes
Jun 12, 2026
Contributor
Author
|
thanks for the review @kylebarron, i added a screenshot from rendering the "feature flags" section locally |
Contributor
|
Thank you @kevinjqliu and @kylebarron |
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
3 participants
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.
Which issue does this PR close?
Closes #749.
Rationale for this change
What changes are included in this PR?
Follow up to #724
PR #724 made
reqwestoptional and introduced*-baseprovider features, but the crate docs only mentioned them in passing. This PR adds three doc sections to the crate-level module docs, grouped at the bottom as a "configuration" cluster:# Feature Flags— Layering rationale + three reference tables (provider, transport/shared, other), coveringcloud-base,cloud,tls-webpki-roots,integration, etc.# Customizing HTTP Clients— Existing section, now cross-references Disabling reqwest.# Disabling reqwest— When to use*-base, aCargo.tomlsnippet, and anAmazonS3Builder::with_http_connectorexample.Per-provider module docs (
aws,azure,gcp,http) now link to the Feature Flags table so readers can see theawsvsaws-basecomparison directly. README gains a## Disabling reqwestsection mirroring the lib.rs explainer alongside the existingwasm32-wasip1build command.Are there any user-facing changes?
No, docs only