Skip to content

CEL conformance test documentation: fix links in markdown #518

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

Open
AustinWise wants to merge 1 commit into
base: master
Choose a base branch
from
Open

CEL conformance test documentation: fix links in markdown #518

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
6 changes: 3 additions & 3 deletions tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ are expected to read the `tests/simple/testdata` files as inputs to the
parse, check, and evaluation behaviors of a given implementation. Reference
implementations may be found in the following locations:

* (cel-go conformance)[https://github.com/google/cel-go/tree/master/conformance]
* (cel-cpp conformance)[https://github.com/google/cel-cpp/tree/master/conformance]
* (cel-java conformance)[https://github.com/google/cel-java/tree/main/conformance/src/test/java/dev/cel/conformance]
* [cel-go conformance](https://github.com/google/cel-go/tree/master/conformance)
* [cel-cpp conformance](https://github.com/google/cel-cpp/tree/master/conformance)
* [cel-java conformance](https://github.com/google/cel-java/tree/main/conformance/src/test/java/dev/cel/conformance)

Each CEL implementation should also have its own unit tests and benchmarks
for testing subcomponents, its API, and other implementation-dependent
Expand Down