Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tried to add some new UI contributions to the plugin.xml and was overwhelmed by its organically grown structure. To address this, I reorganized the file to improve readability and maintainability. I grouped configuration elements by feature, such as outline toolbar contributions, code folding, find references support, and others. This makes it easier to follow the purpose of each section and to contribute new features. For example, adding a new outline toolbar button is now straightforward because all the relevant building blocks are grouped together.
I hope you agree that this refactoring improves the file’s clarity and usability. 🤞
Since the Git diff is not helpful for showing the structural changes, I wrote a small Python script to compare the effective differences between two plugin.xml files. This script allows you to verify that no technical functionality has changed—only the layout has been cleaned up and made more logical.
plugin_xml_diff.py: