cel-rs-rb 0.3.1 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +79 -0
- data/Cargo.lock +877 -0
- data/README.md +55 -20
- data/ext/cel/Cargo.toml +1 -1
- data/ext/cel/src/lib.rs +143 -82
- data/lib/cel/version.rb +1 -1
- data/lib/cel.rb +22 -9
- data/spec/cel_spec.rb +328 -2
- data/spec/packaging_spec.rb +13 -0
- metadata +3 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 43135286f54e827165a6dbb9212d5f39a94511b7689c3f1eb7a36413eaa5a5b0
|
|
4
|
+
data.tar.gz: c5d01546ad8635828a8f6c8d7a2221248eb6cc0e9d3429e149a844d0d393108e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 0bb048ff31fa5cf28ca3610ba820311f3d47afef49a544896dac891b1ac48fcc37ba19b3ed6a802c66b145bdd59e03d731a8fc1584f107ee30bc8646479e6f36
|
|
7
|
+
data.tar.gz: 01c5e7136e4bf206e2b49e2c91b612e9232f5404319cc77f3cbf4106f4f9fd1562eb5cb08c46c687286a568293fffbff79fa74275ca1adde8aaab57b27c7b986
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,50 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.4.0
|
|
4
|
+
|
|
5
|
+
Upgrade to the published [cel 0.16.0](https://crates.io/crates/cel/0.16.0)
|
|
6
|
+
from crates.io. This is a stable release, with no Git dependency or beta updater.
|
|
7
|
+
The [upstream comparison](https://github.com/cel-rust/cel-rust/compare/v0.15.0...v0.16.0)
|
|
8
|
+
is the full dependency change since 0.3.x.
|
|
9
|
+
|
|
10
|
+
### Breaking and behavior changes
|
|
11
|
+
|
|
12
|
+
- Ordering a NaN against any number with `<`, `<=`, `>`, or `>=` now returns
|
|
13
|
+
`false`, in either operand position, instead of raising `CEL::ExecutionError`.
|
|
14
|
+
- `Program#references` excludes comprehension iteration/accumulator bindings and
|
|
15
|
+
removes leading dots from absolute variable and function names.
|
|
16
|
+
- Map membership with an unusable key now returns `false`: `[] in {}` no longer
|
|
17
|
+
raises.
|
|
18
|
+
- Optional indexing and field access suppress only missing-key and out-of-bounds
|
|
19
|
+
errors.
|
|
20
|
+
- List addition now requires another list: `[1] + {'a': 2}` raises
|
|
21
|
+
`CEL::ExecutionError` instead of appending the map's keys.
|
|
22
|
+
- Durations now accept ±315576000000.999999999 seconds (about 10,000 years). Ruby's
|
|
23
|
+
floating-point seconds still cannot preserve every nanosecond at large magnitudes.
|
|
24
|
+
|
|
25
|
+
### Added
|
|
26
|
+
|
|
27
|
+
- `max_iterations:` on `CEL.compile` and `CEL::Program.compile`. The default `0`
|
|
28
|
+
is unlimited; positive unsigned 64-bit integers bound total comprehension
|
|
29
|
+
iterations across nested and sibling loops, with a fresh budget per execution.
|
|
30
|
+
- Per-call `timeout:` (finite, non-negative seconds) and `interrupt:` options on
|
|
31
|
+
`Program#execute`, `#call`, and `#execute_with_context`, plus
|
|
32
|
+
`CEL::CancellationToken.new`, `#cancel!`, and `#cancelled?` for cross-thread
|
|
33
|
+
cancellation.
|
|
34
|
+
- Opt-in `extensions: [:sets]` for `sets.contains`, `sets.equivalent`, and
|
|
35
|
+
`sets.intersects`. Lists are treated as sets: order and duplicates do not matter,
|
|
36
|
+
and numeric elements compare by value.
|
|
37
|
+
- `CEL::Duration::MAX_NANOSECONDS` and `MIN_NANOSECONDS` expose CEL's exact
|
|
38
|
+
inclusive duration limits as Ruby Integers.
|
|
39
|
+
|
|
40
|
+
### Fixed
|
|
41
|
+
|
|
42
|
+
- Failures on secondary Ruby threads now raise the documented `CEL::ParseError`,
|
|
43
|
+
`CEL::ExecutionError`, and `CEL::TypeError`, rather than plain `RuntimeError`.
|
|
44
|
+
- Release replaced Ruby callbacks and their captured values instead of retaining
|
|
45
|
+
every registration until the `CEL::Context` is collected. In-flight executions
|
|
46
|
+
keep their original callbacks alive.
|
|
47
|
+
|
|
3
48
|
## 0.3.1
|
|
4
49
|
|
|
5
50
|
### Fixed
|
|
@@ -8,3 +53,37 @@
|
|
|
8
53
|
`CEL::Context` is reachable. Prevents use-after-free after the caller drops its
|
|
9
54
|
own reference and Ruby runs garbage collection. Callbacks are also pinned during
|
|
10
55
|
compaction, including when collection runs inside a callback.
|
|
56
|
+
|
|
57
|
+
## 0.3.0
|
|
58
|
+
|
|
59
|
+
Upgrade from cel 0.13 to [cel 0.15.0](https://github.com/cel-rust/cel-rust/releases/tag/v0.15.0).
|
|
60
|
+
|
|
61
|
+
### Breaking and behavior changes
|
|
62
|
+
|
|
63
|
+
- List/map `.contains(value)` is no longer supported; use `value in collection`.
|
|
64
|
+
`.contains()` only accepts strings.
|
|
65
|
+
- Map literals with duplicate keys raise `CEL::ExecutionError`.
|
|
66
|
+
- String `size()` counts Unicode code points rather than bytes.
|
|
67
|
+
- `string(bytes)` rejects invalid UTF-8.
|
|
68
|
+
- Numeric conversions reject out-of-range results, and parsed timestamps and
|
|
69
|
+
durations must fit CEL's allowed ranges.
|
|
70
|
+
- `all()` and `exists()` can absorb an earlier evaluation error when a later
|
|
71
|
+
element determines the result.
|
|
72
|
+
- Ruby callbacks cannot shadow standard CEL builtins in default contexts.
|
|
73
|
+
Conflicts raise `CEL::ExecutionError` during execution, even if the expression
|
|
74
|
+
does not call the conflicting function. Empty contexts have no builtin conflicts;
|
|
75
|
+
registering the same custom callback name again still replaces its callback.
|
|
76
|
+
|
|
77
|
+
### Added
|
|
78
|
+
|
|
79
|
+
- Compilation uses the standard CEL environment, including optional access and
|
|
80
|
+
the `optMap` / `optFlatMap` macros.
|
|
81
|
+
- Opt-in `extensions:` for the strings, lists, math, and encoders libraries.
|
|
82
|
+
|
|
83
|
+
### Compatibility
|
|
84
|
+
|
|
85
|
+
- Default contexts retain `max` and `min` for compatibility with cel 0.13 even
|
|
86
|
+
though upstream removed them from its defaults. Ruby callbacks can still replace
|
|
87
|
+
these two functions; empty contexts do not register them.
|
|
88
|
+
- CEL values without a Ruby conversion, including opaque values, raise
|
|
89
|
+
`CEL::TypeError` when returned to Ruby.
|