Skip to content

[Ruleset Engine] Update partial #19962

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 13, 2025
Merged

[Ruleset Engine] Update partial #19962

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions src/content/docs/ruleset-engine/rules-language/values.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,7 @@ It is not possible to define your own arrays. You can only use arrays returned b

<Render
file="rules-language-missing-value-behavior"
params={{ one: "an out-of-bounds array index" }}
params={{ errorDescription: "an out-of-bounds array index" }}
/>

You can only use `[*]` multiple times in the same expression if applied to the same array. Also, you can only use `[*]` in the first argument of a function call.
Expand Down Expand Up @@ -217,7 +217,7 @@ It is not possible to define your own maps. You can only use maps returned by fi

<Render
file="rules-language-missing-value-behavior"
params={{ one: "a non-existing key in a map" }}
params={{ errorDescription: "a non-existing key in a map" }}
/>

## Lists
Expand Down
12 changes: 5 additions & 7 deletions src/content/partials/ruleset-engine/rules-language-missing-value-behavior.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,9 @@
---
inputParameters: errorDescription

params:
- errorDescription
---

import { Markdown } from "~/components"

Accessing {props.one} produces a "missing value". A missing value has the following behavior:
Accessing {props.errorDescription} produces a "missing value". A missing value has the following behavior:

* Any comparison `<expr> <op> <literal>` where `<expr>` evaluates to a missing value will evaluate to false.
* Function calls like `function(<expr>)`, where `<expr>` evaluates to a missing value, will return a missing value in most cases, but the exact behavior can vary per function.
- Any comparison `<expr> <op> <literal>` where `<expr>` evaluates to a missing value will evaluate to false.
- Function calls like `function(<expr>)`, where `<expr>` evaluates to a missing value, will return a missing value in most cases, but the exact behavior can vary per function.
Loading