Skip to main content

Parent Component Object

Deprecated

This node is deprecated and kept only so existing projects keep working. It is not offered in the node picker for new use.

Deprecated access to the parent component's instance state. Use Parent Component Object (net.noodl.ParentComponentObject).

The legacy Parent Component State node read and wrote the enclosing parent component's instance-scoped state — the role now filled by Parent Component Object and Set Parent Component Object Properties. Deprecated and hidden from the picker.

When to use it​

Do not use in new graphs — use net.noodl.ParentComponentObject (with Set Parent Component Object Properties) instead.

At a glance​

CategoryComponent Utilities
Type nameParent Component State
Available inbrowser
SSR compatibilitysafe
Provided bynoodl-viewer-react
Behaviour specnot written yet

Inputs​

Values​

NameTypeDefaultDescription
propertiesStringlist—Names of the parent values to expose, each becoming a matching input and output

Signals​

NameTypeDefaultDescription
fetchSignal—Republishes every property from the parent; connecting this stops the outputs updating on their own
storeSignal—Writes the supplied property values into the parent component object

Outputs​

Signals​

NameTypeDefaultDescription
changedSignal—Fires when a property on the resolved parent is written, unless Fetch is connected
fetchedSignal—Fires once Fetch has republished every property
storedSignal—Fires once Set has written every property

Dynamic ports​

This node's port list changes at runtime (runtime-discovered); the tables above may be incomplete for a given instance.

Some ports are discovered at runtime from user code, parameters or connected components, and are pushed to the editor per instance; the static port list below is incomplete for such instances.

Ports at runtime​

Property ports are generated from the per-instance properties list (runtime-discovered).

Parent Component Object, Set Parent Component Object Properties

Code export​

Does not export to React yet. A project that uses it exports with this node named in the export report.

Why: deliberately out of scope — the type is deprecated in the catalog, so nobody building today is offered one. A project that still holds one exports it as a named deferral, which is the right answer for a node its own editor has retired.

How export works shows what an export writes, with a worked example.

Generated

This page is generated from node-catalog-enriched.json, the node's spec in packages/nodegx-node-spec and the export ledger. Do not edit it by hand — run npm run docs:nodes to regenerate, and fix the source instead.