From 61d64df57dbf9618e2944dbf44e515d261fe8987 Mon Sep 17 00:00:00 2001 From: Graham Esau Date: Fri, 26 Mar 2021 23:59:35 +0000 Subject: [PATCH] v0.8.2 --- CHANGELOG.md | 2 +- docs/3-generating.md | 3 +-- docs/4-features.md | 1 + docs/examples/8-enum_repr.md | 1 - docs/examples/9-from_value.md | 1 - schemars/Cargo.toml | 4 ++-- schemars_derive/Cargo.toml | 2 +- 7 files changed, 6 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8183622..4033b69 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@ # Changelog -## [0.8.2] - **In-dev** +## [0.8.2] - 2021-03-27 ### Added: - Enable generating a schema from any serializable value using `schema_for_value!(...)` macro or `SchemaGenerator::root_schema_for_value()`/`SchemaGenerator::into_root_schema_for_value()` methods (https://github.com/GREsau/schemars/pull/75) - `#[derive(JsonSchema_repr)]` can be used on C-like enums for generating a serde_repr-compatible schema (https://github.com/GREsau/schemars/pull/76) diff --git a/docs/3-generating.md b/docs/3-generating.md index e9cf09e..f8a284f 100644 --- a/docs/3-generating.md +++ b/docs/3-generating.md @@ -20,7 +20,6 @@ If you want more control over how the schema is generated, you can use the [`gen See the API documentation for more info on how to use those types for custom schema generation. - +```