Skip to content

Conversation

@matthiasbeyer
Copy link
Member

This is a bit of a shameless self-plug. The mentioned type_description crate was a by-product of some work @TheNeikos and I have done and we've used it already to do exactly what the article describes.

Maybe @TheNeikos wants to add some comments before this gets considered, so this goes as draft for now.

@@ -0,0 +1,46 @@
# Rendering documentation for your Configuration
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you open a discussion for us to discuss this first?

There are a lot of potential directions to go and I tend to prefer the solution discover to happen in issues as PRs are more likely to come and go.

Comment on lines 19 to +20
- [Rendering documentation for your CLI apps](./in-depth/docs.md)
- [Rendering documentation for your Configuration](./in-depth/render-configuration.md)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you feel is the line for this being in the CLI documentation vs being in its own page?

You could render them straight to the terminal, so that a user can "ask" your
app what configuration it provides:

```commandline
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we tend to use console

myapp print-config-options
```

Using the [type_description crate](https://crates.io/crates/type_description)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should update the list of referenced crates at the end of the book

Comment on lines +16 to +32
```rust,ignore
use type_description::AsTypeDescription;
use type_description::TypeDescription;
use type_description::TypeKind;
use type_description::Sign;
/// A configuration
#[derive(TypeDescription)]
struct Config {
/// The bind address
addr: std::net::SocketAddr,
/// The Port
port: u16,
}
```

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All code samples should be extracted from full programs that we compile in CI and can be run.

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