Introduce UuidParseError #286
No reviewers
Labels
No labels
breaking
bug
dependencies
good first issue
help wanted
unstable
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-uuid-rs/uuid!286
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/uuid_parse_error"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm submitting a(n) feature,refactor
Description
Replace ParseError with UuidParseError
Motivation
Currently, the context for the errors around uuid string is limited to hyphenated, integer, simple and urn formats. This expands the error layout so that the context is more generic so nonstandard formats can use our error type for custom uuids.
Tests
Fix current tests to match the new signature. No new tests added
Related Issue(s)
closes #276
explain multiple segment count.
Parsers can expect a range of Uuid segment count.
github.com/uuid-rs/uuid@1be44122d8/src/parser/mod.rs (L62-L67)This comment was generated by todo based on a
TODOcomment in1be44122d8in #286. cc @uuid-rs.remove the u8 cast
this only needed until we switch to
github.com/uuid-rs/uuid@ec26b6051f/src/lib.rs (L173-L178)This comment was generated by todo based on a
TODOcomment inec26b6051fin #286. cc @uuid-rs.@ -0,0 +9,4 @@// option. This file may not be copied, modified, or distributed// except according to those terms.use core::fmt;you don't need the
<'a>on impl@ -0,0 +9,4 @@// option. This file may not be copied, modified, or distributed// except according to those terms.use core::fmt;oops
@Dylan-DPC ready for review + merge
bors: r+
Build succeeded