Embedded Object

Defines a base class for objects that exist as a child property of a Node object.

Remarks

Overview

An Embedded Object is a configurable item in Grooper that is always owned by another object, typically as a property of a Node. Embedded Objects are not standalone—they are designed to be part of a larger configuration, such as a command, resource, or settings object within a Node or another Connected Object.

Embedded Objects inherit their database context and repository relationships from their owner, ensuring that all operations and references are performed within the correct scope. This design enables modular, reusable configuration components that can be managed as part of a parent object's settings or structure.

Key Features

• Ownership:
  Every Embedded Object is associated with a parent Connected Object, which determines its database context, permissions, and repository relationships. The owner is set at creation and can be updated as needed.

• Hierarchical Configuration:
  Embedded Objects allow complex configuration structures by enabling objects to contain other configurable objects as properties. This supports modular design, encapsulation of logic, and reuse of configuration components.

• Context Inheritance:
  Embedded Objects automatically inherit the database connection, project, and resource folders from their owner, ensuring consistent access to repository resources and settings.

• Writeability:
  The ability to modify an Embedded Object is determined by its owner's write permissions, ensuring that configuration changes respect repository security and integrity.