You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 04a204c
Browse filesBrowse the repository at this point in the historyBrowse files
test(harness): compare_nulls — cazar present-null vs absent-key (wave B #4)
normalizeValue dropeaba los null de los mapas JSON, así que un campo que TS
emite como null y Go omite (o viceversa) comparaba igual. Nuevo opt-out
'compare_nulls: true' que conserva los null. Aplicado a los casos-envelope
resolve-dependencies-success y read-configuration.features-configuration — pasan,
o sea TS/Go coinciden en null-vs-absent y ahora se compara de verdad.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/migration/parity-matrix.yaml
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -447,6 +447,7 @@ initial_cases:
447
447
class: feature-resolution
448
448
current_status: match
449
449
compare_hashes: true
450
+
compare_nulls: true
450
451
451
452
- id: read-configuration.compose-path-terminal
452
453
lane: semantic
@@ -2314,6 +2315,7 @@ initial_cases:
2314
2315
class: features-runtime
2315
2316
current_status: match
2316
2317
compare_hashes: true
2318
+
compare_nulls: true
2317
2319
notes: "stdout = grafo mermaid + JSON installOrder. El mermaid se genera con roundPriority 0 (default TS) y alias del feature id (fallback a ref.ID cuando falta la annotation); los hashes de nodo se scrubbean por reMermaidNode. installOrder resuelto vía ComputeInstallationOrder."
0 commit comments