Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fixes in README #1035

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
Oct 1, 2024
Merged

Fixes in README #1035

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
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ against some input. Checking is optional, but strongly encouraged.

### Environment Setup

Let's expose `name` and `group` variables to CEL using the `cel.Declarations`
Let's expose `name` and `group` variables to CEL using the `cel.Variable`
environment option:

```go
Expand Down Expand Up @@ -93,7 +93,7 @@ if err != nil {
The `cel.Program` generated at the end of parse and check is stateless,
thread-safe, and cachable.

Type-checking in an optional, but strongly encouraged, step that can reject some
Type-checking is an optional, but strongly encouraged step that can reject some
semantically invalid expressions using static analysis. Additionally, the check
produces metadata which can improve function invocation performance and object
field selection at evaluation-time.
Expand Down Expand Up @@ -244,8 +244,8 @@ too may offer a WASM evaluator with direct to WASM compilation.

### Do I need to Parse _and_ Check?

Checking is an optional, but strongly suggested, step in CEL expression
validation. It is sufficient in some cases to simply Parse and rely on the
Checking is an optional, but strongly suggested step in CEL expression
validation. It is sufficient in some cases to simply parse and rely on the
runtime bindings and error handling to do the right thing.

### Where can I learn more about the language?
Expand Down