fix: don't duplicate field-level ops when filtering by child array path (v0.17.2)

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code

[maxjay]

Summary

• Changing a field on a child item and calling diff(childArrayPath, { includeUnchanged: true }) returned two ops for the changed item: the element-level Replace AND a loose field-level Replace that leaked out of .changes
• Root cause: flattenOpsForFilter recursed into Replace.changes even when the parent Replace already matched the path prefix
• Fix replaces it with filterOpsForPrefixes, which only recurses into .changes when the parent op does not match — keeping field ops nested where they belong
• Bumps patch to 0.17.2

Root cause in detail

After #35 landed, path-filtered diffs used flattenOpsForFilter to expose ops nested inside Replace.changes (needed when a parent element changes but you're querying its children). The problem: it flattened unconditionally, so when the parent Replace itself already matched the prefix, its changes contents were also emitted at the top level — duplicating the field op.

Example: diff('$.secondaryTaskTypes', { includeUnchanged: true }) with one field changed on item 4:

• Before fix: [Unchanged×4, Replace(item4), Replace(approvalWorkflow)] ← 6 ops, field op duplicated
• After fix: [Unchanged×4, Replace(item4)] ← 5 ops, field op stays inside Replace.changes

Changes

src/engine.ts — replace flattenOpsForFilter with filterOpsForPrefixes: include a matching op as-is; only recurse into .changes when the op itself doesn't match.

src/engine.array-semantics.test.ts — new regression test: "field change on one child: returns one Replace op for that child — not a duplicate field-level op"

Test plan

• 255 tests pass
• Changing one field on a child item returns exactly one Replace op for that child
• The field-level op is accessible via .changes on the element Replace, not as a separate top-level entry
• All prior includeUnchanged propagation behaviour from fix: propagate includeUnchanged into nested keyed array diffs (v0.17.1) #35 continues to work

https://claude.ai/code/session_017H6NzxYAwbmKxHH6QusCdh

---

Generated by Claude Code