Create a custom behavior
Behaviors add functionality to the Portable Text Editor (PTE) in a declarative way.
For a deep dive into behaviors and how they work, check out Behaviors.
Import the behavior helper
Begin by importing defineBehavior
.
Define the behavior
Behaviors need three things:
- A triggering event. See the full list of events.
- A guard, or condition that determines if this behavior should apply.
- An action to invoke if the event and guard are met.
Here’s an example behavior:
Let’s break it down:
- It listens for the
insert.text
event. You can use any native or synthetic event here. - The guard checks if the text that triggered this event is equal to a lowercase
a
. The guard is true and the behavior will perform the actions. - It sends an
insert.text
action with with “A” instead of “a”.
Understanding Behaviors Learn more about how each part of the Behavior API works.
Register the behavior
In order to use the behavior, add it to the EditorProvider
. If you want to avoid overwriting the default behaviors, import them and register them with your custom behavior.