Intermediate Output Document does not collect results from parent changes
Closed this issue · 0 comments
nikitawootten-nist commented
Describe the bug
When the base comparison collects results from the comparison document, it finds all changes that match the specified pattern (for example, controls) and merges them into one list. This does not account for parent changes, such as a group being added or deleted.
Expected behavior
Parent ArrayChanged' leftOnly and rightOnly fields should be traversed when assembling the intermediate output document of a base comparison.
Other Comments
Also a related problem that I do not have details on yet: some conditions cause the excel output document to produce bad output (no matched controls, no changes) that causes the table formatter and conditional formatting rules to break.