usage-validation 6.7.1

Portable expression validation for usage specs
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

[package]
name = "usage-validation"
description = "Portable expression validation for usage specs"
version = "6.7.1"
edition = "2021"
rust-version = "1.91"
homepage = { workspace = true }
documentation = { workspace = true }
repository = { workspace = true }
authors = { workspace = true }
license = { workspace = true }

[dependencies]
# Defaults off, `regex` back on. A spec's `validate=` sees one string and returns a boolean, so
# the dates, the JSON codec and base64 that expr-lang ships by default are 12 crates a CLI
# compiles to evaluate `int(value) > 0`. `matches` stays because dropping it would make the
# same expression pass in Go and fail here, and the spec reference promises that generated
# Rust and Go parsers enforce the same rule — `conformance/validation.json` has the vectors.
expr-lang = { version = "2.1.0", default-features = false, features = ["regex"] }

[package.metadata.release]
shared-version = true
release = true