refactor(tree): clarify move logic#27466
Conversation
|
Hi! Thank you for opening this PR. Want me to review it? Based on the diff (212 lines, 3 files), I've queued these reviewers:
How this works
|
| expectJsonTree(tree, expectedState); | ||
| }); | ||
|
|
||
| it("can move a node out from a field and into a field under a sibling", () => { |
There was a problem hiding this comment.
This scenario is now covered in src/test/feature-libraries/default-field-kinds/defaultChangeFamily.spec.ts.
jason-ha
left a comment
There was a problem hiding this comment.
Cool - additional flow/clarity suggestions
Co-authored-by: Jason Hartman <jasonha@microsoft.com>
| { parent: root, field: fooKey }, | ||
| 1, | ||
| 3, | ||
| { parent: root_bar0, field: barKey }, |
There was a problem hiding this comment.
nit: would be nice to name the path: root.bar[0].bar, yes?
Description
Clarifies the logic of
DefaultEditBuilder.moveand adds more test coverage.Breaking Changes
None