Google celebrates Pride Month. See how.

Component monikers

A component moniker identifies a specific component instance in the component tree using a topological path.

This section describes the syntax used for displaying monikers to users.


Instance and Collection Names

Parents assign names to each of their children. Dynamically created children are arranged by their parent into named collections.

Syntax: Each name follows the regex [-_.a-z0-9]{1,100}. That is, a string of 1-100 of the following characters: a-z, 0-9, _, ., -.

See the component manifest reference for more details.

Child Monikers

Represented by the child's collection name (if any) and the child's name delimited by :.

Syntax: {name} or {collection}:{name}


  • carol
  • support:dan - The collection support with the child dan.

Relative Monikers

Represented by the minimal sequence of child monikers encountered when tracing downwards to the target.

A relative path begins with . and alternates path segments (/) and component/collection names. Relative monikers do not support upward traversal (i.e. ..) (from child to parent).

Syntax: ./{path from ancestor to target}


  • . - self - no traversal needed
  • ./carol - a child - traverse down carol
  • ./carol/sandy - a grandchild - traverse down carol then down sandy
  • ./support:dan - a child - traverse down into collection child support:dan

Absolute Monikers

Represented by the absolute path from the root to the component as a sequence of child monikers.

An absolute path begins with / and is followed by downwards traversal path segments delimited by /. There is no trailing /.

Syntax: /{path from root to target}


  • / - the root itself (it has no name because it has no parent)
  • /alice/support:dan - from root traverse down alice then down support:dan
  • /alice/carol - from root traverse down alice then down carol