Idea Summary
Working Copy Compare should display all detected application changes, even when a component type is not supported for automatic merge.

Currently, changes to certain application-level components (for example Plugins or Componont Settings) may not appear in the Compare dialog at all. This can lead developers to believe that a Working Copy has been fully merged, while additional manual synchronization steps are still required.

Displaying these changes would improve transparency and reduce the risk of incomplete merges.

Use Case
A developer creates a Working Copy and modifies one or more Plugins or Component Settings.

When the Working Copy is compared with the main application, these changes are not shown in the Compare results. During the merge process, the developer sees no indication that additional changes exist outside the displayed differences.

As a result, modifications to Plugins or Component Settings can easily be forgotten and remain missing from the main application after the merge.

This is particularly problematic in team development scenarios where developers rely on the Compare view as the authoritative source of differences between a Working Copy and the main application.

Preferred Solution (Optional)
Enhance the Compare dialog to display all detected changes, including components that cannot be merged automatically. In the Merge dialog, clearly highlight the changes that will remain after merging and must be resolved manually.