Pair unique layer-only shape changes
This commit is contained in:
parent
87683db7e8
commit
ab308f7b7f
2 changed files with 253 additions and 38 deletions
|
|
@ -68,6 +68,8 @@ displayed rows gets one legend entry. Object details use `-` for removals, `+` f
|
|||
and `~` for likely replacements. Identical unmatched objects share a row
|
||||
with a count such as `+ 12× 1/0: path …`. Unmatched paths with five or more
|
||||
vertices show their width, vertex count, and vertex bounds in one line.
|
||||
A unique polygon, box, or path replacement that differs only in layer or
|
||||
datatype appears on one row, for example `~ 1/0 (WG) → 2/0 (CORE) · rectangle`.
|
||||
|
||||
Use `--format json` for details of individual objects and `--hierarchy` to see
|
||||
which parent cells are affected.
|
||||
|
|
@ -128,8 +130,9 @@ comparison, totals, or exit status. A layer display filter hides references
|
|||
without a numeric layer. `--max-changes N` limits displayed object occurrences
|
||||
after filtering. Text defaults to 100 occurrences and shows a replacement only
|
||||
when both objects fit within the limit. Grouped rows count each object toward
|
||||
the limit. A single omission line lists changes hidden by filters or the
|
||||
limit. JSON has no default object limit and reports
|
||||
the limit. When a layer filter selects one side of a layer-only replacement,
|
||||
that side appears as an addition or removal. A single omission line lists
|
||||
changes hidden by filters or the limit. JSON has no default object limit and reports
|
||||
omissions from both display filters and any explicit limit in `report_selection`.
|
||||
See the [JSON reference](diff-reports.md) for the selection counters.
|
||||
|
||||
|
|
|
|||
|
|
@ -90,9 +90,12 @@ explicit defaults remain significant. For gzip inputs, source offsets locate
|
|||
records in the decompressed layout.
|
||||
|
||||
Replacements link report-local removed/added IDs with `match_rule`,
|
||||
`field_changes`, and `properties_changed`. Rules are `unique_kind_layer_bounds`,
|
||||
`unique_kind_layer`, or `unique_kind_target`. IDs are not persistent identities;
|
||||
ambiguous candidates stay separate. Explanation text is for display only.
|
||||
`field_changes`, and `properties_changed`. The `unique_layer_change` rule
|
||||
matches a unique polygon, box, or path on each side with identical retained
|
||||
fields and properties outside the layer and datatype fields. The other rules
|
||||
are `unique_kind_layer_bounds`, `unique_kind_layer`, and `unique_kind_target`.
|
||||
Ambiguous candidates stay separate. Replacement IDs refer only to objects in
|
||||
the current report. Explanation text is for display only.
|
||||
|
||||
## Diagnostics and hierarchy
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue