Packages

spectra

0.3.2
0.13.4 0.13.3 0.13.2 0.13.1 0.13.0 0.12.1 0.12.0 0.11.4 0.11.3 0.11.2 0.11.1 0.11.0 0.10.0 0.9.4 0.9.3 0.9.2 0.9.1 0.9.0 0.8.2 0.8.1 0.8.0 0.7.0 0.6.0 0.5.1 0.5.0 0.4.0 0.3.2 0.3.1 0.3.0 0.2.0 0.1.10 0.1.9 0.1.8 0.1.7 0.1.6 0.1.5 0.1.4 0.1.3 0.1.2 0.1.1 0.1.0

Type safe data (de) serialization.

HexDocs

Current section

Files

Jump to
Readme
41 Versions
0 Dependencies
Dependants
Files
Activity
spectra CHANGELOG.md
Raw

CHANGELOG.md 

# Changelog



All notable changes to this project will be documented in this file.



The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),

and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).



## [0.3.2] - 2026-01-25



### Changed

- Improved documentation and clarified OTP 27 requirement



## [0.3.0] - 2026-01-20



### Changed

- Upgraded JSON Schema from draft-07 to 2020-12 specification with proper `$schema` field support

- Upgraded OpenAPI spec generation from 3.0 to 3.1 (which natively uses JSON Schema 2020-12)

- Improved remote type handling in enums and parameterized types

- Simplified error handling implementation in preparation for better error messages

- Enhanced null/optional handling with clearer documentation and dedicated tests for undefined/nil behavior in mandatory vs optional map fields



### Internal

- Refactored type utilities into `spectra_util.erl` with renamed functions for consistency

- New tests for typed map fields, parameterized remote types, and enum remote types

- Property-based testing for JSON encoding/schema/decoding consistency (`test/prop_json_encode_schema_consistency.erl`)

- Python validators for JSON Schema 2020-12 and OpenAPI 3.1 standards compliance

- Development tooling improvements including updated `.tool-versions` and enhanced `Makefile` with release safeguards

- Major code simplification in `spectra_binary_string.erl`, `spectra_json.erl`, and `spectra_string.erl`

- Created `sp_error.erl` module for consolidated error handling



## [0.2.0] - 2025-12-14



### Changed

- **Breaking**: Extra fields in JSON objects are now ignored during deserialization instead of causing a `not_matched_fields` error. This affects map, struct (elixir) and record deserialization.



### Notes

- The old strict validation behavior has been commented out with a TODO to potentially add it back as a configuration option in the future