minted
3.1.1, released 2 months ago by an unverified publisher
Shared vocabulary types and outcomes for the minted family of domain-parsing packages.
What it does
Provides the core vocabulary types (ParseOutcome, MintedFailure, and MintedFormatError) used across minted domain packages to handle parsing without throwing exceptions. It serves as the base library that sibling packages like minted_contact or minted_finance depend on.
AI-written summary of version 3.1.1, based on the package's README and metadata. Report an inaccuracy
Use it when
- You are building or using sibling packages in the minted family that require shared parse outcome types.
- You want to reference ParseOutcome or MintedFailure directly in your codebase.
Skip it when
- You want specific domain value types like Email, Iban, or Date without adding their respective domain packages.
- You prefer standard validation that returns booleans or strings rather than parse outcomes.
Strengths
- Provides a unified, type-safe parse outcome structure across different domain models.
- Pure Dart with zero heavy platform dependencies.
Weaknesses
- Contains no domain parsing engines on its own; requires sibling packages for actual domain types.
- Single-value extension types can be incorrectly bypassed via casting if not careful.
Setup
- Kind
- Pure Dart
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 2
Add minted to pubspec.yaml alongside any specific minted_* domain packages you need.
switch (Iban.parse(input)) {
case ParseSuccess(:final value): send(value);
case ParseFailure(:final reason): log(reason.message);
}Alternatives
Packages that do the same job and could replace minted.
- validators2
String validation and sanitization for Dart.
83Compare - result_type
A Result type representing success or failure in Dart
50Compare - brotli
Pure Dart Brotli decoder
50Compare - icalendar_parser
Package to parse iCalendar (.ics) files written in pure Dart.
50Compare