Community
Participate
Working Groups
hi, every time I'm playing with new extension point (say every 2-3 months), the biggest pain is to figure out how to read the registry using extension registry API. I mean problems like: - which of Platform.getExtensionRegistry().get* methods should be used - jumping back and forth betwen extension point schema and the handler class to correctly read all the arguments, etc. - should I use registry tracer, to make the code more flexible (honestly, I never did that, after finishing basic ext.point reader) Because all this things are pretty straightforward and repeatable, it would be really nice to have a generator producing all above code. Such generator could be accessible somewhere from the extension point schema editor. The produced code could use all the latest and greatest API. Probably such generated code would still need some manual modifications to integrate with ready stuff, but that's not a big issue.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.