NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
A robust and type-safe library for parsing API responses and converting error codes into user-friendly messages with comprehensive error handling and validation.
Last release 11 months ago
27 Oct 2025
Ships unpredictably
gaps range from 2 weeks to 2.2 years
Nearly every release is documented
notes for 6 of 6 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
6 releases · first in 2023
One column per quarter.
NEW: Added optional meta field support in error messages
meta field support in error messages
ErrorMessageEntity.meta - nullable Map<String, dynamic> for dynamic error metadatameta field with arbitrary data structurenull when not provided by backendmetaInt(String key) - safely get integer valuesmetaDouble(String key) - safely get double valuesmetaStr(String key) - safely get string valuesmetaBool(String key) - safely get boolean valuesmetaMap(String key) - safely get nested map valuesinterpolate(String template) method
{key} placeholders with values from meta"Min {min}, max {max}" → "Min 8, max 20"toString() method includes meta fieldmeta field is null for responses without metadataexample/meta_usage_guide.md for detailed usage examplesmeta is parsed only if present and is a valid Mapnull (graceful degradation)NEW: Support for simplified API response format
fromJsonSafe method automatically detects response typeParseResult<T> return types{"id": 1, "name": "Tom"}{"errors": [...]}fromJsonSafe now returns ParseResult<ApiResponseEntity<T>> instead of direct entityresult.dataOrThrow or result.dataOrNull to access parsed dataREMOVED: Complete pagination logic and related classes
ApiResponsePagination and ApiResponsePaginationEntityPagination and PaginationEntity classesParserResponseWithPaginationEntityApiParserSuccessResponse (removed pagination field)ApiParserSuccessResponse no longer has pagination fieldPagination logic was removed to keep the library focused on its core responsibility: error parsing and message handling. Pagination is better handled at the application level or in dedicated data layer components.
Added ability to parse lists at the root of JSON responses. Added fromJsonList method to ApiResponseEntity class.
Added hashCode and operator for ParseMessageEntity and ErrorSourceEntity to compare object when testing bloc(integration tests).
Initial version with basic API error parsing functionality
Your coding agent can read these notes before it upgrades. Set up the MCP server →