Sandbox / type

ComponentList

Sandbox.ComponentList

Overview

Declared type and relationship surface; behavioural intent is not inferred from the metadata alone.

ComponentList is a declared class in the pinned release metadata.

Type relationships

Base type

—

Interfaces

—

Declarations owned by this type

• Sandbox.ComponentList.Create(Sandbox.TypeDescription,System.Boolean) method
• Sandbox.ComponentList.Create(System.Boolean) method
• Sandbox.ComponentList.FirstOrDefault(System.Func`2<Sandbox.Component,System.Boolean>) method
• Sandbox.ComponentList.ForEach(System.String,System.Boolean,System.Action`1<Sandbox.Component>) method
• Sandbox.ComponentList.ForEach(System.String,System.Boolean,System.Action`1<T>) method
• Sandbox.ComponentList.Get(Sandbox.FindMode) method
• Sandbox.ComponentList.Get(System.Boolean) method
• Sandbox.ComponentList.Get(System.Guid) method
• Sandbox.ComponentList.Get(System.Type,Sandbox.FindMode) method
• Sandbox.ComponentList.GetAll() method
• Sandbox.ComponentList.GetAll(Sandbox.FindMode) method
• Sandbox.ComponentList.GetAll(Sandbox.FindMode) method
• Sandbox.ComponentList.GetAll(System.Type,Sandbox.FindMode) method
• Sandbox.ComponentList.GetInAncestors(System.Boolean) method
• Sandbox.ComponentList.GetInAncestorsOrSelf(System.Boolean) method
• Sandbox.ComponentList.GetInChildren(System.Boolean) method
• Sandbox.ComponentList.GetInChildrenOrSelf(System.Boolean) method
• Sandbox.ComponentList.GetInDescendants(System.Boolean) method
• Sandbox.ComponentList.GetInDescendantsOrSelf(System.Boolean) method
• Sandbox.ComponentList.GetInParent(System.Boolean) method
• Sandbox.ComponentList.GetInParentOrSelf(System.Boolean) method
• Sandbox.ComponentList.GetOrCreate(Sandbox.FindMode) method
• Sandbox.ComponentList.Move(Sandbox.Component,System.Int32) method
• Sandbox.ComponentList.TryGet(out T,Sandbox.FindMode) method
• Sandbox.ComponentList.Count property

Inherited members

Direct inherited members are not expanded here because the pinned record does not establish a complete inheritance closure.

Flow

The diagram separates the declared inputs, operation and result. Connections describe the recorded relationship; they do not establish execution order or lifecycle behaviour.

Open this operation in the flow explorer →

Examples

No reviewed code example or workflow covers this declaration. Use the exact declaration and inputs/outputs flow as the available local teaching surface, then run a bounded installed-build probe before relying on behaviour. Open the exact declaration flow.

Constraints and pitfalls

• Execution context: game-or-shared-unknown
• A public declaration is not proof of sandbox allowlisting.
• No compile/runtime verification was run.

Prerequisites and limits

• Resolve the type identity in the pinned release before relying on its declaration.

Still unknown

• Installed-build callability, compile behaviour and runtime effects are not established by this snapshot.

declaration-and-sourcemetadata-and-source-only

Evidence and verification

Related workflows

None selected.

Related diagrams

None selected.