Sandbox / type
MemberDescription
Sandbox.MemberDescription Overview
Declared type and relationship surface; behavioural intent is not inferred from the metadata alone.
Generated declaration summary
MemberDescription is a declared class in the pinned release metadata.
Automatically derived from the pinned declaration; this is not a reviewed tutorial or runtime test.
Exact identity & snapshot
Type relationships
Declarations owned by this type
- Sandbox.MemberDescription.GetCustomAttribute() method
- Sandbox.MemberDescription.GetDisplayInfo() method
- Sandbox.MemberDescription.HasAttribute() method
- Sandbox.MemberDescription.HasAttribute(System.Type) method
- Sandbox.MemberDescription.HasTag(System.String) method
- Sandbox.MemberDescription.IsNamed(System.String) method
- Sandbox.MemberDescription.Aliases property
- Sandbox.MemberDescription.Attributes property
- Sandbox.MemberDescription.DeclaringType property
- Sandbox.MemberDescription.Description property
- Sandbox.MemberDescription.Group property
- Sandbox.MemberDescription.Icon property
- Sandbox.MemberDescription.Identity property
- Sandbox.MemberDescription.IsFamily property
- Sandbox.MemberDescription.IsField property
- Sandbox.MemberDescription.IsMethod property
- Sandbox.MemberDescription.IsProperty property
- Sandbox.MemberDescription.IsPublic property
- Sandbox.MemberDescription.IsStatic property
- Sandbox.MemberDescription.Name property
- Sandbox.MemberDescription.Order property
- Sandbox.MemberDescription.ReadOnly property
- Sandbox.MemberDescription.SourceFile property
- Sandbox.MemberDescription.SourceLine property
- Sandbox.MemberDescription.Tags property
- Sandbox.MemberDescription.Title property
- Sandbox.MemberDescription.TypeDescription 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.
- No indexed implementation-source chunk is linked to this declaration; the entry is declaration-only.
declaration-onlymetadata-only
Upstream documentation availability
Documentation text is not copied into this export because the release metadata redistribution licence is unresolved.
Evidence and verification
pinned metadata source correspondence unverified
- declaration: pinned-release-metadata
Installed-build compile/runtime state: not run.
Related workflows
None selected.
Related diagrams
None selected.