-
Notifications
You must be signed in to change notification settings - Fork 99
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
feat: add form-js extensions blogpost #171
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,196 @@ | ||
--- | ||
|
||
title: Create custom form components | ||
description: "Introducing newest form-js extension capabilities to create custom form components." | ||
preview_image: http://bpmn.io/assets/attachments/blog/2023/005-range-validate.png | ||
layout: blogpost.hbs | ||
slug: 2023-custom-form-components | ||
author: | ||
- Niklas Kiefer <https://github.com/pinussilvestrus> | ||
published: 2023-11-01 18:00 | ||
|
||
releases: | ||
- '[email protected]' | ||
|
||
--- | ||
|
||
<p class="introduction"> | ||
We are excited to inform you about the latest [form-js](https://github.com/bpmn-io/form-js) improvements that add new extension capabilities to create custom form components. It is easier now to use existing form-js components in your custom renderers and provide properties panel extensions. | ||
</p> | ||
|
||
<!-- continue --> | ||
|
||
The ability to create custom form components was [a long-awaited feature](https://github.com/bpmn-io/form-js/issues/123). With the recent [email protected] release, we added extension features to the toolkit in the nature of common bpmn-io extension patterns. | ||
|
||
Check out [our example](https://github.com/bpmn-io/form-js-examples/tree/master/custom-components) to gather more insights about the new extension capabilities. | ||
|
||
## Define a custom form component renderer | ||
|
||
Creating and registering custom form components with a [Preact](https://github.com/preactjs/preact) component was already possible. It is now also possible to use existing core form-js components in the renderer. | ||
|
||
```javascript | ||
import { | ||
Errors, | ||
Description, | ||
Label | ||
} from '@bpmn-io/form-js'; | ||
|
||
import { | ||
html | ||
} from 'diagram-js/lib/ui'; | ||
|
||
export function RangeRenderer(props) { | ||
|
||
// ... | ||
|
||
return html`<div class="my-component-wrapper"> | ||
<${Label} | ||
id=${ prefixId(id, formId) } | ||
label=${ label } /> | ||
<div class="my-form-component"> | ||
// ... | ||
</div> | ||
<${Description} description=${ description } /> | ||
<${Errors} errors=${ errors } id=${ errorMessageId } /> | ||
</div>`; | ||
} | ||
``` | ||
|
||
<div class="figure full-size"> | ||
<a href="https://demo.bpmn.io/form"> | ||
<img src="{{ assets }}/attachments/blog/2023/005-range-validate.png" alt="The custom range component in the form viewer."> | ||
</a> | ||
|
||
<p class="caption"> | ||
Render a custom range component into the form viewer. | ||
</p> | ||
</div> | ||
|
||
We also added new options to a form field `config` object. For example, you can now define the default properties panel entries that should be shown in the form editor. You can also specify an icon for the form component. | ||
|
||
```javascript | ||
import { | ||
Numberfield | ||
} from '@bpmn-io/form-js'; | ||
|
||
RangeRenderer.config = { | ||
|
||
/* we can even extend the configuration of existing fields */ | ||
...Numberfield.config, | ||
type: rangeType, | ||
label: 'Range', | ||
iconUrl: `data:image/svg+xml,${ encodeURIComponent(RangeIcon) }`, | ||
propertiesPanelEntries: [ | ||
'key', | ||
'label', | ||
'description', | ||
'min', | ||
'max', | ||
'disabled', | ||
'readonly' | ||
] | ||
}; | ||
``` | ||
|
||
That's all! The component library and properties panel will be automatically updated with the new form component, and the renderer will take over the rendering of the form component. | ||
|
||
<div class="figure full-size"> | ||
<a href="https://demo.bpmn.io/form"> | ||
<img src="{{ assets }}/attachments/blog/2023/005-range-palette.png" alt="The component library with the custom range component"> | ||
</a> | ||
|
||
<p class="caption"> | ||
The custom range component gets populated into the component library. | ||
</p> | ||
</div> | ||
|
||
|
||
<div class="figure condensed-size"> | ||
<a href="https://demo.bpmn.io/form"> | ||
<img src="{{ assets }}/attachments/blog/2023/005-range-properties.png" alt="The properties panel with default entries for the custom range component"> | ||
</a> | ||
|
||
<p class="caption"> | ||
Re-use existing properties entries. | ||
</p> | ||
</div> | ||
|
||
Please find out more about [rendering extensions](https://github.com/bpmn-io/form-js-examples/tree/master/custom-components#add-a-custom-form-component-renderer) in our dedicated example. | ||
|
||
|
||
## Create a properties panel extension | ||
|
||
We added the ability to extend the properties panel with custom entries. We mirrored the [proven provider architecture](https://bpmn.io/blog/posts/2022-new-properties-panel-foundation.html) of other bpmn.io properties panel libraries. | ||
|
||
Next to the `propertiesPanelEntries` we described above, you can create a properties provider that can add, remove, and modify existing entries. | ||
|
||
```javascript | ||
export class CustomPropertiesProvider { | ||
constructor(propertiesPanel) { | ||
propertiesPanel.registerProvider(this, 500); | ||
} | ||
|
||
getGroups(field, editField) { | ||
|
||
... | ||
return (groups) => { | ||
|
||
if (field.type !== 'range') { | ||
return groups; | ||
} | ||
|
||
const generalIdx = findGroupIdx(groups, 'general'); | ||
|
||
groups.splice(generalIdx + 1, 0, { | ||
id: 'range', | ||
label: 'Range', | ||
entries: RangeEntries(field, editField) | ||
}); | ||
|
||
return groups; | ||
}; | ||
} | ||
} | ||
``` | ||
|
||
<div class="figure full-size"> | ||
<a href="https://demo.bpmn.io/form"> | ||
<img src="{{ assets }}/attachments/blog/2023/005-range-custom-entries.png" alt="Custom properties panel entries for the range component"> | ||
</a> | ||
|
||
<p class="caption"> | ||
Custom properties panel entries for the range component. | ||
</p> | ||
</div> | ||
|
||
Find out more about [properties panel extensions](https://github.com/bpmn-io/form-js-examples/tree/master/custom-components#add-custom-properties-panel-entries) in our dedicated example. | ||
|
||
|
||
## 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. | ||
|
||
|
||
```javascript | ||
import { FormPlayground } from '@bpmn-io/form-js'; | ||
|
||
new FormPlayground({ | ||
container, | ||
schema, | ||
data, | ||
additionalModules: [ | ||
RenderExtension | ||
], | ||
editorAdditionalModules: [ | ||
PropertiesPanelExtension | ||
] | ||
}); | ||
``` | ||
|
||
## Wrapping Up | ||
|
||
We'd love to hear your feedback on the new extension capabilities. We are looking forward to seeing what you build upon the new features! | ||
|
||
Did we miss anything? Did you spot a bug, or would you like to suggest an improvement? Reach out to us via [our forums](https://forum.bpmn.io/), tweet us [@bpmn_io](https://twitter.com/bpmn_io), or file an issue you found in [the form-js issue tracker](https://github.com/bpmn-io/form-js/issues). | ||
|
||
Get the latest Forms modeling toolkit pre-packaged or as source code via [npm](https://www.npmjs.com/package/@bpmn-io/form-js) or [unpkg](https://unpkg.com/@bpmn-io/form-js). |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should we give an example of
viewerAdditionalModules
too?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 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.