From b1ec92b56321d775450244975e6fb8dff7cc5d36 Mon Sep 17 00:00:00 2001 From: kanarus Date: Sat, 13 Dec 2025 20:04:02 +0900 Subject: [PATCH 1/2] v0.3.2 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0175e89..5ba975c 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,7 @@ If you have no pain on this, you may not need `serdev`. ```toml [dependencies] -serdev = "0.3" +serdev = { version = "0.3", features = ["derive"] } serde_json = "1.0" ``` From 471306bb1cdd382036a90082e63b21f2e4b9634c Mon Sep 17 00:00:00 2001 From: kanarus Date: Sat, 13 Dec 2025 20:06:46 +0900 Subject: [PATCH 2/2] fix README a bit --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5ba975c..7f361e3 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,7 @@ impl TryFrom for ValidPoint { } ``` -This is, actually, (almost) exactly what `serdev` does! +Actually, this is (almost) exactly what `serdev` does! Such manual implementation may be a trigger of mistakes like using `Point` directly for parsing user's input. `serdev` eliminates such kind of mistakes, automatically performing the specified validation. @@ -67,7 +67,7 @@ Indeed this doesn't cause such misuses, but produces boilerplate... (more and mo --- `#[serde(validate)]` makes, for a struct having complicated conditions, its `Deserialize` itself the valid `parse`r of the struct, -in a clean way with near-zero boilerplate. +with near-zero boilerplate. If you have no pain on this, you may not need `serdev`.