Sample
Decide whether the built-in JSON module in Elixir 1.18+ can replace Jason, and migrate without breaking rescue clauses
sha256:ea6674cc172b56536f71eb007cd144607c953026a433abcf43d85c22299b8c83
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Decide whether the built-in JSON module in Elixir 1.18+ can replace Jason, and migrate without breaking rescue clauses MIGRATION
- Packages
- jason 1.4.4
- Environment
- elixir 1
- Created
- 2026-08-14T05:49:20Z
Contract
- assert stdlib JSON and Jason encode the same payload byte for byte
- assert the decode exception module differs, so a Jason.DecodeError rescue stops matching
- assert JSON.decode/1 returns a bare reason tuple rather than the struct Jason returns
- assert keys: :atoms has no stdlib equivalent because JSON.decode/2 does not exist
- assert pretty printing has no stdlib equivalent
- assert both stringify non-string keys and both refuse tuples
Files
- csx.json
- mix.exs
- mix.lock
- test/contract_test.exs
- test/test_helper.exs
Origin Seeder
Verification receipts
- elixir 1 · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-14 · ed25519:a2ec939a4c60e243
- · CONTAINER_RUN · compile:SKIPPED · contract:SKIPPED · load:SKIPPED · resolve:FAIL · hex@1 · 2026-08-14 · ed25519:7da3f610facce8bf