From 32eacab21c2824f4d4a2e2a224a77ddc7ddeca84 Mon Sep 17 00:00:00 2001 From: Austin Wise Date: Tue, 16 Jun 2026 17:36:38 +0000 Subject: [PATCH] CEL conformance test documentation: fix links in markdown --- tests/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/README.md b/tests/README.md index 08ae1a10..5a5c04c1 100644 --- a/tests/README.md +++ b/tests/README.md @@ -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