Crates.io | type_description |
lib.rs | type_description |
version | 0.5.0 |
source | src |
created_at | 2022-07-29 09:35:15.558182 |
updated_at | 2023-05-16 13:58:48.108708 |
description | Machine-readable type descriptions |
homepage | |
repository | https://github.com/TheNeikos/type_description |
max_upload_size | |
id | 634898 |
size | 118,377 |
This crate provides machine-readable descriptions for types.
For a general overview, please check out the guide.
The idea is to make types discoverable for users by explaining them in a way
that a user can understand without knowing implementation details (a u16
is
an "integer with 16 bit")
One could make configuration types explained with this crate and show the explanation (in a GUI, web interface, some special config-editor) to the user.
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,
}
let desc = Config::as_type_description();
assert_eq!(desc.name(), "Config");
assert_eq!(desc.doc(), Some("A configuration"));
assert!(std::matches!(desc.kind(), TypeKind::Struct(_)));
match desc.kind() {
TypeKind::Struct(v) => {
let first_field = &v[0];
assert_eq!(first_field.name(), "addr");
assert_eq!(first_field.doc(), Some("The bind address"));
assert_eq!(first_field.kind().name(), "String");
assert_eq!(first_field.kind().doc(), Some("A socket address"));
assert_eq!(*first_field.kind().kind(), type_description::TypeKind::String);
let second_field = &v[1];
assert_eq!(second_field.name(), "port");
assert_eq!(second_field.doc(), Some("The Port"));
assert_eq!(second_field.kind().name(), "Integer");
assert_eq!(second_field.kind().doc(), Some("An unsigned integer with 16 bits"));
assert_eq!(*second_field.kind().kind(), type_description::TypeKind::Integer { size: 16, sign: Sign::Unsigned });
}
_ => unreachable!()
}
This crate contains a AsTypeDescription
implementation for various third party crates.
The up to date list can be found on docs.rs.
serde
model and be compatible with all
serde::{Deserialize, Serialize}
typesAsTypeDescription
TypeDescription
(serde::Deserialize
should be preferred for that)MPL-2.0