-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#1668] API types to simplify work with launch configuration attributes #1669
base: master
Are you sure you want to change the base?
Conversation
ruspl-afed
commented
Dec 19, 2024
•
edited
Loading
edited
- identify launch attribute
- connect it with preference metadata (to supply defaults/label/description)
- read attribute from configuration
- write attribute to configuration working copy
- demonstrate usage for ExternalTools
This pull request changes some projects for the first time in this development cycle.
An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patch
Further information are available in Common Build Issues - Missing version increments. |
Test Results 1 668 files - 87 1 668 suites - 87 1h 11m 7s ⏱️ - 29m 56s Results for commit 0eaee71. ± Comparison against base commit 29bc65f. This pull request removes 597 tests.
♻️ This comment has been updated with latest results. |
As mentioned in the call, some example using this API proposal would be helpful. There is probably some content in org.eclipse.ui.externaltools/External Tools Base/org/eclipse/ui/externaltools/internal/launchConfigurations you can tweak to leverage this API. |
87da722
to
ceac906
Compare
…uration attributes * identify launch attribute * connect it with preference metadata (to supply defaults/label/description) * read attribute from configuration * write attribute to configuration working copy * demonstrate usage for ExternalTools
I'm not sure why it is is failing @HannesWell
|
It looks like your change is breaking API-tools^^ |
Thank you @HannesWell for your assistance.
WOW! But that wasn't part of my plan. It looks like this issue was already reported. Interesting, may be I can have a deeper look to it soon. And still interested in your feedback regarding PR content. |