taler-docs

commit 4b4fba2eb54103a0d037533f416dad922a972e4f
parent d9d2a345b497f3b92fa4ff4a56aa7bdef8e882a9
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Mon, 12 Jan 2026 08:16:26 +0900

fix misc. minor issues, add FIXMEs

Diffstat:
M
core/api-merchant.rst
 | 
25
++++++++++++++++---------

1 file changed, 16 insertions(+), 9 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -5734,7 +5734,7 @@ Using template
 
     interface WalletTemplateDetails {
 
-      // Hard-coded information about the contrac terms
+      // Hard-coded information about the contract terms
       // for this template.
       template_contract: TemplateContractDetails;
 
@@ -5876,8 +5876,8 @@ Using template
 
   **Request:**
 
-  The request must be a `UsingTemplateDetails` and we accept JSON application and URL encoded.
-
+  The request must be a `UsingTemplateDetailsRequest` and we accept JSON application and URL encoded.
+  
 
   **Response:**
 
@@ -5886,13 +5886,20 @@ Using template
 
   **Details:**
 
+  FIXME: This is not the correct style of doing it. We should
+  use a union type (|) and include a field (template_type)
+  to make it explicit which of the structures is being used
+  (even if the backend knows what to expect, it is better for
+  parsers and clarity; make the template_type optional and
+  default to "fixed-order" if omitted for backwards-compatibility!)
+  
   Based on the template type, provide one of the following request bodies:
 
-  1. For ``fixed-order``, use `UsingTemplateDetails`.
+  1. For ``fixed-order``, use `UsingTemplateDetailsRequest`.
 
-  .. ts:def:: UsingTemplateDetails
+  .. ts:def:: UsingTemplateDetailsRequest
 
-    interface UsingTemplateDetails {
+    interface UsingTemplateDetailsRequest {
 
       // Summary of the template
       summary?: string;
@@ -5901,11 +5908,11 @@ Using template
       amount?: Amount;
     }
 
-  2. For ``inventory-cart``, use `UsingTemplateDetailsInventory`.
+  2. For ``inventory-cart``, use `UsingTemplateDetailsInventoryRequest`.
 
-  .. ts:def:: UsingTemplateDetailsInventory
+  .. ts:def:: UsingTemplateDetailsInventoryRequest
 
-    interface UsingTemplateDetailsInventory {
+    interface UsingTemplateDetailsInventoryRequest {
 
       // Summary of the template
       summary?: string;