Skip to content

Document that the client/server features are now opt-in #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

edmorley
Copy link

@edmorley edmorley commented Feb 26, 2022

Adds documentation for the switch to the client and server features now being opt-in, rather than enabled by default (see #54).

I experimented with also enabling the nightly-only doc_cfg / doc_auto_cfg features (that allow showing feature labels in the docs, see rust-lang/rust/issues/43781), however:

  • the features don't currently work well with the re-exports in the crate root, so require every struct/trait to be manually annotated.
  • the rendering isn't great - the crate landing page wrapping ended up broken
  • (to a lesser extent) whilst these can be used on docs.rs (since it builds docs with nightly), they won't work for the GitHub pages version of the docs this project uses to preview main.

So for now it seems best to not use that.

I did adjust the docs.rs config in Cargo.toml to ensure docs are actually generated for all features, since otherwise the docs were almost empty after #54.

I also fixed a few typos / markdown syntax errors (let me know if you'd prefer these in a separate PR).

Adds documentation for the switch to the `client` and `server` features now
being opt-in, rather than enabled by default (see softprops#54).

I experimented with also enabling the nightly-only `doc_cfg` / `doc_auto_cfg`
features (see rust-lang/rust/issues/43781, which can be used on `docs.rs` since
it builds docs with nightly), however:
- the features don't currently work well with the re-exports in the crate root,
  so require every struct/trait to be manually annotated.
- the rendering isn't great - the crate landing page wrapping ended up broken

So for now it seems best to not use that.

I did adjust the `docs.rs` config in `Cargo.toml` to ensure docs are actually
generated for all features, since previously the docs were almost empty.

I also fixed a few typos / markdown syntax errors.
@edmorley edmorley mentioned this pull request Feb 26, 2022
@edmorley edmorley mentioned this pull request Mar 5, 2022
@onalante-msft
Copy link
Contributor

Sorry this took so long to review. I had this on my to-do and forgot about it.

@edmorley
Copy link
Author

edmorley commented Apr 1, 2022

@onalante-msft No need to be sorry! Thank you for taking a look :-)

@edmorley
Copy link
Author

We've since dropped this as a (transitive) dependency so are no longer using this crate. Closing the PR to clean up my open PRs list.

@edmorley edmorley closed this Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants