Comparing states
Compare shows the difference between two snapshots, or between a snapshot and the current project (“what changed since my last snapshot?”). Compare is read-only; editing is paused while you review.
What Layertrail detects
Section titled “What Layertrail detects”Layertrail compares nodes by their stable internal identity, not by their position in a text file. That is why it can tell you a node moved rather than reporting one deletion and one unrelated addition.
| Change | Meaning |
|---|---|
| Added | The node exists only in the newer state. |
| Removed | The node exists only in the older state. Removing a parent also lists what was removed with it, and flags references from other nodes that now point at nothing. |
| Moved | The node has a different parent. |
| Renamed | Same node, new name. |
| Reordered | Same parent, different position among siblings. |
| Property changed | A value was added, removed, or edited, shown with before and after. |
| Template changed | The node now uses a different template, or none. |
| Schema change | A template, or one of its fields or options, was added, removed, or edited. Listed separately from node changes. |
The comparison panel leads with a short list of the most important findings, followed by totals and the project tree with each change marked in place.
Comparing one part of the project
Section titled “Comparing one part of the project”Select a node, such as a rack, and compare just that subtree. The scope includes the node and everything beneath it in either state, so a device that moved in or out of the rack is still shown. Totals and reports cover only the scope, and the scope’s path is shown in the header and every export.
What a comparison does not say
Section titled “What a comparison does not say”A comparison reports what is different. It doesn’t claim that a change caused a test result. Snapshot descriptions are where you record what you observed, and the HTML review ends with the same reminder.
To share a comparison, see Sharing a review.