feat: add form-js extensions blogpost #171
Conversation
pinussilvestrus
force-pushed
the
170-form-extensions
branch
from
88ecf73 to
7b35b9f
Compare
pinussilvestrus
force-pushed
the
170-form-extensions
branch
from
7b35b9f to
ce921c1
Compare
pinussilvestrus
requested review from
vsgoulart,
christian-konrad,
a team,
smbea and
barmac
and removed request for
a team
|
The example is still pending to be merged, but feel free to already review this post 👍 |
bpmn-io-tasks
bot
added
needs review
|
Wow, this is so cool! I think this blog post could be published as is. |
|
|
||
| ## Plugging everything together | ||
|
|
||
| You can plug your custom modules into the different form-js components as `viewerAdditionalModules` and `editorAdditionalModules`. With the latest release, we also added the `additionalModules` option that allows you to provide extensions to both simultaneously, for example, the renderer. |
There was a problem hiding this comment.
Should we give an example of viewerAdditionalModules too?
There was a problem hiding this comment.
I would have to think of a proper use case. In which case you'd like to have an extension for the viewer only, but not for the editor? In terms of a custom renderer you have to add to both anyways.
One example that comes into my mind is if you want to have a different rendering in both components. We do that for the text component, where it looks different in viewer and editor (placeholder only). Maybe that could be something to showcase.
|
Really nice one! 👏 |
Closes #170
This adds a dedicated blog post about form-js custom components.
Depends on https://github.com/camunda/team-hto/issues/372
Depends on bpmn-io/form-js-examples#7