summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2021-08-01 11:41:55 +0200
committerChristian Grothoff <christian@grothoff.org>2021-08-01 11:42:00 +0200
commita52f2c77edab063734abcd1cc736367d3d1d4be5 (patch)
treee4a0bccf0032feaf436682b8bd82fad16adc23c0
parente6c3b7bd3ad2c14e4424832a31b74c2e833e3a6c (diff)
downloaddocs-a52f2c77edab063734abcd1cc736367d3d1d4be5.tar.gz
docs-a52f2c77edab063734abcd1cc736367d3d1d4be5.tar.bz2
docs-a52f2c77edab063734abcd1cc736367d3d1d4be5.zip
-update spec following #6942
-rw-r--r--core/api-merchant.rst7
1 files changed, 3 insertions, 4 deletions
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index ac2ba86..8a39278 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -1477,9 +1477,8 @@ Reserving inventory
interface LockRequest {
// UUID that identifies the frontend performing the lock
- // It is suggested that clients use a timeflake for this,
- // see https://github.com/anthonynsimon/timeflake
- lock_uuid: UUID;
+ // Must be unique for the lifetime of the lock.
+ lock_uuid: String;
// How long does the frontend intend to hold the lock?
duration: RelativeTime;
@@ -1603,7 +1602,7 @@ Creating orders
// be used in case different UUIDs were used for different
// products (i.e. in case the user started with multiple
// shopping sessions that were combined during checkout).
- lock_uuids?: UUID[];
+ lock_uuids: String[];
// Should a token for claiming the order be generated?
// False can make sense if the ORDER_ID is sufficiently