Sample
Prevent Equatable from evaluating objects containing maps with distinct keys as equal when missing keys evaluate to null on lookup.
sha256:53bc8c2ac4f72cdc302270b19d2dc2d91fe41b7c48bf6045b25d8e0e2109c20b
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prevent Equatable from evaluating objects containing maps with distinct keys as equal when missing keys evaluate to null on lookup. HOW
- Packages
- equatable 2.0.8
- Environment
- dart
- Created
- 2026-08-17T02:07:05Z
Commonly assumed
Equatable evaluates two instances holding maps with different keys as non-equal even if all values in those maps are null.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Comparing Equatable objects containing maps with disjoint keys like {'keyA': null} and {'keyB': null} evaluates to false because missing keys are checked with containsKey rather than resolving to null.
- Equatable props map comparison correctly checks key existence when values are null.
Files
- NOTES.md
- csx.json
- pubspec.lock
- pubspec.yaml
- test/contract.dart
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- dart 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · pub@1 · 2026-08-17 · ed25519:d91480838ac982c9