Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes #6206; using cuboid rather than cube #6691

Merged
merged 1 commit into from
Apr 10, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/content/policy-language.md
Original file line number Diff line number Diff line change
Expand Up @@ -311,17 +311,17 @@ A simple example is a regex to match a valid Rego variable. With a regular strin

Composite values define collections. In simple cases, composite values can be treated as constants like [Scalar Values](#scalar-values):

```live:eg/cube:module
cube := {"width": 3, "height": 4, "depth": 5}
```live:eg/cuboid:module
cuboid := {"width": 3, "height": 4, "depth": 5}
```

The result:

```live:eg/cube:query:merge_down
cube.width
```live:eg/cuboid:query:merge_down
cuboid.width
```

```live:eg/cube:output
```live:eg/cuboid:output
```

Composite values can also be defined in terms of [Variables](#variables) or [References](#references). For example:
Expand Down Expand Up @@ -382,11 +382,11 @@ collections of unique values. Just like other composite values, sets can be
defined in terms of scalars, variables, references, and other composite values.
For example:

```live:eg/cube/sets:query:merge_down
s := {cube.width, cube.height, cube.depth}
```live:eg/cuboid/sets:query:merge_down
s := {cuboid.width, cuboid.height, cuboid.depth}
```

```live:eg/cube/sets:output
```live:eg/cuboid/sets:output
```

> Set documents are collections of values without keys. OPA represents set
Expand Down
Loading