Documentation ¶
Overview ¶
Package containers defines types and functions for resolving qualified names within a namespace or type provided to CEL.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type Container ¶
type Container struct {
// contains filtered or unexported fields
}
Container holds a reference to an optional qualified container name and set of aliases.
The program container can be used to simplify variable, function, and type specification within CEL programs and behaves more or less like a C++ namespace. See ResolveCandidateNames for more details.
func NewContainer ¶
func NewContainer(opts ...ContainerOption) (*Container, error)
NewContainer creates a new Container with the fully-qualified name.
func (*Container) Extend ¶
func (c *Container) Extend(opts ...ContainerOption) (*Container, error)
Extend creates a new Container with the existing settings and applies a series of ContainerOptions to further configure the new container.
func (*Container) Name ¶
Name returns the fully-qualified name of the container.
The name may conceptually be a namespace, package, or type.
func (*Container) ResolveCandidateNames ¶
ResolveCandidateNames returns the candidates name of namespaced identifiers in C++ resolution order.
Names which shadow other names are returned first. If a name includes a leading dot ('.'), the name is treated as an absolute identifier which cannot be shadowed.
Given a container name a.b.c.M.N and a type name R.s, this will deliver in order:
a.b.c.M.N.R.s a.b.c.M.R.s a.b.c.R.s a.b.R.s a.R.s R.s
If aliases or abbreviations are configured for the container, then alias names will take precedence over containerized names.
type ContainerOption ¶
ContainerOption specifies a functional configuration option for a Container.
Note, ContainerOption implementations must be able to handle nil container inputs.
func Abbrevs ¶
func Abbrevs(qualifiedNames ...string) ContainerOption
Abbrevs configures a set of simple names as abbreviations for fully-qualified names.
An abbreviation (abbrev for short) is a simple name that expands to a fully-qualified name. Abbreviations can be useful when working with variables, functions, and especially types from multiple namespaces:
// CEL object construction qual.pkg.version.ObjTypeName{ field: alt.container.ver.FieldTypeName{value: ...} }
Only one the qualified names above may be used as the CEL container, so at least one of these references must be a long qualified name within an otherwise short CEL program. Using the following abbreviations, the program becomes much simpler:
// CEL Go option Abbrevs("qual.pkg.version.ObjTypeName", "alt.container.ver.FieldTypeName") // Simplified Object construction ObjTypeName{field: FieldTypeName{value: ...}}
There are a few rules for the qualified names and the simple abbreviations generated from them: - Qualified names must be dot-delimited, e.g. `package.subpkg.name`. - The last element in the qualified name is the abbreviation. - Abbreviations must not collide with each other. - The abbreviation must not collide with unqualified names in use.
Abbreviations are distinct from container-based references in the following important ways:
- Abbreviations must expand to a fully-qualified name.
- Expanded abbreviations do not participate in namespace resolution.
- Abbreviation expansion is done instead of the container search for a matching identifier.
- Containers follow C++ namespace resolution rules with searches from the most qualified name to the least qualified name.
- Container references within the CEL program may be relative, and are resolved to fully qualified names at either type-check time or program plan time, whichever comes first.
If there is ever a case where an identifier could be in both the container and as an abbreviation, the abbreviation wins as this will ensure that the meaning of a program is preserved between compilations even as the container evolves.
func Alias ¶
func Alias(qualifiedName, alias string) ContainerOption
Alias associates a fully-qualified name with a user-defined alias.
In general, Abbrevs is preferred to Alias since the names generated from the Abbrevs option are more easily traced back to source code. The Alias option is useful for propagating alias configuration from one Container instance to another, and may also be useful for remapping poorly chosen protobuf message / package names.
Note: all of the rules that apply to Abbrevs also apply to Alias.
func Name ¶
func Name(name string) ContainerOption
Name sets the fully-qualified name of the Container.