-
Notifications
You must be signed in to change notification settings - Fork 199
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
Support multiple tab providers #438
Conversation
This adds the PropertiesPanel#registerProvider method that allows users to register custom properties providers. A provider must have one of the following signatures: ({ getTabs: (element) => any[] }) // returns / overrides existing tabs ({ getTabs: (element) => (any[]) => any[] }); // may modify the existing tabs (i.e. monkey patch) and return the updated tabs Related to camunda/camunda-modeler#1992
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like that 👏
I created an example plugin to verify it works with the Camunda Modeler: https://github.com/pinussilvestrus/properties-provider-plugin-example. Super smooth to update the tabs 👍
I'd go for merging it, but I'm also ok to wait for another voice to review it. The next step would then be to update the element-templates-modal plugin to consume the new API.
Aaa, I was searching for the place the Camunda Modeler hooks into the properties panel. Thanks for the 👉. |
If you think it is fine, please add your 👍. We generally practice four eyes, not many eyes 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎸
This implements a tab provider mechanism similar to the one we bpmn-js uses for palette and context pad.
Required by camunda/camunda-modeler#1992.