Feature request
When a flow contains the same processor type in several process groups, the current flat list under Flow Changes makes it hard to locate exactly which group each change belongs to.
Proposed change
Group the diff output by the process group where each changed component lives. Each group gets its own header showing the full path from the root, followed by the changes that belong to it.
Example of the new output format
#### Flow Changes
**`RootFlow`** — 5 changes
- A Processor of type `GenerateFlowFile` named `My Processor` has been added...
- In Processor of type `UpdateAttribute` named `Update`, the value of property...
**`RootFlow > Ingestion Group`** — 2 changes
- In Processor of type `InvokeHTTP` named `Call API`, the Run Schedule changed...
**`RootFlow > Processing Group`** — 1 change
- A Processor of type `UpdateAttribute` named `Enrich` has been added...
**`(Parameter Contexts)`** — 1 change
- In the Parameter Context `MyContext`, the value of parameter `api.url` has changed...
Notes
- Parameter context changes (value edits, adds/removes inside a context) are grouped under a synthetic
(Parameter Contexts) section at the bottom.
- Bundle changes remain in their own separate Bundle Changes section as today.
- Visual-only diffs (position, size, style) continue to be silently dropped.
Feature request
When a flow contains the same processor type in several process groups, the current flat list under Flow Changes makes it hard to locate exactly which group each change belongs to.
Proposed change
Group the diff output by the process group where each changed component lives. Each group gets its own header showing the full path from the root, followed by the changes that belong to it.
Example of the new output format
Notes
(Parameter Contexts)section at the bottom.