fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1)

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code

[maxjay]

$(cat <<'EOF'

Summary

• diffArrayByKey hard-coded includeUnchanged: false when recursing into matched element pairs, so calling diff('$.orders[0].lineItems', { includeUnchanged: true }) always returned [] — nested Unchanged ops were never emitted
• Fix threads the flag through correctly and extends the path filter to look inside Replace.changes
• Bumps patch version to 0.17.1

Root cause

Three separate issues compounded:

1. Line 638 of engine.ts — diffNode for element pairs was called with false instead of includeUnchanged, stripping the flag before it could reach nested keyed arrays
2. fieldsChanged detection — used fieldOps.length > 0; once fix 1 landed, Unchanged ops in fieldOps would falsely mark an unchanged element as changed
3. Path filter in _diff — only searched top-level ops; when the parent element had changed, child ops lived inside Replace.changes and were invisible to the filter

Changes

src/engine.ts

• Pass includeUnchanged (not false) into the nested diffNode call in diffArrayByKey
• Change fieldsChanged to fieldOps.some(op => op.op !== OpType.Unchanged)
• For unchanged elements: push fieldOps directly to ops so path filters can reach children
• Add flattenOpsForFilter helper; use it in _diff before path-filtering so Replace.changes is also searched

src/engine.array-semantics.test.ts

• New describe block: diff — includeUnchanged propagation into nested keyed arrays
• 5 cases using an orders → lineItems schema (keyed by ref / sku): no changes, child removed, child added, parent-field-only change, sibling isolation

Test plan

• All 254 existing tests continue to pass
• 5 new regression tests cover the reported scenarios
• diff(childPath, { includeUnchanged: true }) returns Unchanged ops when nothing has changed
• diff(childPath, { includeUnchanged: true }) returns correct mix of Add/Remove/Unchanged when children change
• Querying children of a parent whose other fields changed still returns child Unchanged ops

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh
EOF
)

---

Generated by Claude Code