Skip to content

v0.3.2 #37

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.

Sign up for GitHub

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

Merged
kanarus merged 2 commits into from
Dec 13, 2025
Merged

v0.3.2 #37

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b1ec92b
v0.3.2
kanarus Dec 13, 2025
471306b
fix README a bit
kanarus Dec 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ impl TryFrom<Point> 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.
Expand All @@ -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`.

Expand All @@ -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"
```

Expand Down