[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] 01/02: fix regex
From: |
gnunet |
Subject: |
[taler-docs] 01/02: fix regex |
Date: |
Mon, 19 Apr 2021 14:42:19 +0200 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository docs.
commit ca6c47313cb010448a6881a94d183cad1ed94337
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Apr 19 11:51:37 2021 +0200
fix regex
---
design-documents/018-contract-json.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/design-documents/018-contract-json.rst
b/design-documents/018-contract-json.rst
index 7c62600..4208feb 100644
--- a/design-documents/018-contract-json.rst
+++ b/design-documents/018-contract-json.rst
@@ -46,7 +46,7 @@ In order to make it easy to get a canonical representation
for JSON contract
terms, the following restrictions apply:
* Member names are restricted: Only strings matching the regular expression
- ``0-9A-Z_a-z`` or the literal names ``$forgettable`` or ``$forgotten`` are
+ ``^[0-9A-Z_a-z]+$`` or the literal names ``$forgettable`` or ``$forgotten``
are
allowed. This makes the sorting of object members easier, as RFC8785
requires sorting by UTF-16 code points.
* Floating point numbers are forbidden. Numbers must be integers in the range
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.