-
Notifications
You must be signed in to change notification settings - Fork 62
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
Use extendPluggableElement for context menu items #2229
Conversation
May be helpful to look at the diff ignoring whitespace. |
Codecov Report
@@ Coverage Diff @@
## main #2229 +/- ##
==========================================
- Coverage 62.89% 62.81% -0.08%
==========================================
Files 484 484
Lines 22724 22693 -31
Branches 5157 5133 -24
==========================================
- Hits 14292 14255 -37
- Misses 8162 8168 +6
Partials 270 270
Continue to review full report at Codecov.
|
Looks fine to me as is. There is opportunity to use extension points more directly for context menu items though, such as each display making a 'MyDisplay-contextMenuItems' extension point and letting other plugins add to that |
I think this is a good change as well. It is breaking since it removes the previously recommend addAdditionalContextMenuItems approach but I'd say we can go for it |
4b88afa
to
554be88
Compare
Fixed up a merge conflict here, and moved the large dotplot onClick callback to a new function ...should be good to go now though |
554be88
to
40bfb3e
Compare
Inspired by #2226, this makes it so that plugins that want to add context menu items to displays now do so using the
Core-extendPluggableElement
extension point. This removes the need for there to be an autorun that watches for new displays and adds "additionalContextMenuItems" to them. Instead, it extends the display state model itself so all instances of the display already have the additional context menu items.