Component Object
This node accesses the internal state object of the current component.
The Component Object node allows a component to store and retrieve its own private data.
The Component Object node provides a way for a component to maintain internal state that persists as long as the component is alive. It acts like a local database record for the component instance. You can define properties on it and read/write them.
Properties
| Data | Description |
|---|
| Properties | A comma-separated list of property names to manage (e.g., "count,isActive"). Adding names here creates dynamic input/output ports. |
Property Values
| Data | Description |
|---|
| * | Dynamic inputs for each property defined in Properties. Setting a value here updates the state. |
Actions
| Signal | Description |
|---|
| Fetch | Manually retrieves values. |
Outputs
Property Values
| Data | Description |
|---|
| * | Dynamic outputs for each property. |
Changed Events
| Signal | Description |
|---|
| * Changed | Dynamic signals triggered when a specific property changes. |
| Changed | Triggered when any property changes. |
Usage
Use this to create stateful components without relying on global variables.
Example: Counter Component
- Set Properties to
count.
- Connect
count output to count input (via an Addition node to increment).
- The component now remembers its own count.
Detailed Behavior
- Instance Scoped: Every instance of the component has its own separate state object.
- Persistence: State is lost if the component is unmounted (e.g., navigating away or removing from list).
Troubleshooting
- Inputs/Outputs Missing: You must type property names into the Properties field for ports to appear.