summaryrefslogtreecommitdiff
path: root/site
diff options
context:
space:
mode:
authorpommicket <pommicket@gmail.com>2025-09-09 23:27:53 -0400
committerpommicket <pommicket@gmail.com>2025-09-09 23:27:53 -0400
commit18fc4f7c6e758118efff186fa09507c162732c59 (patch)
tree211db7a5f9d2673d9ff107a23599b0c1caa1b64d /site
parent7539affac22f5aa1275b62fa9dc42043d8762795 (diff)
Relax rules around min/max schema keys
Diffstat (limited to 'site')
-rw-r--r--site/spec.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/site/spec.html b/site/spec.html
index f5cb5e2..2e45352 100644
--- a/site/spec.html
+++ b/site/spec.html
@@ -542,10 +542,10 @@ and for my.nephews.car.id is Any (no schema key matches, so the default is used)
</p>
<h3><code>min</code>, <code>max</code> rules</h3>
<p>
- This schema key’s value sets the minimum/maximum value for the key’s value.
- This may only be set if <code>type</code> explicitly allows numeric values
- (i.e. it contains a type <code>Int</code>/<code>UInt</code>/<code>Float</code>).
- The value must be a valid <code>Float</code> (may contain a decimal even if the type is just <code>Int</code>).
+ This schema key’s value must be a valid <code>Float</code> as described above.
+ It sets the minimum/maximum value for configuration keys’ values.
+ It only applies if the configuration key’s value
+ can be parsed as a <code>Float</code>.
</p>
<h3><code>maxlength</code> rule</h3>
<p>