summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRicardo Wurmus <rekado@elephly.net>2021-03-07 13:08:35 +0100
committerRicardo Wurmus <rekado@elephly.net>2021-03-07 13:08:35 +0100
commit28420d0421afbf9b0a56b3e7498ac44a8dee306f (patch)
tree9e8412f4461b928036cfab6ac0b675c582d3fc68
parentb76ae8c42a2198fa206b472c2a6a5dbef257925b (diff)
README: Add TODO item.
-rw-r--r--README.org2
1 files changed, 2 insertions, 0 deletions
diff --git a/README.org b/README.org
index c2e20a1..ef82472 100644
--- a/README.org
+++ b/README.org
@@ -113,3 +113,5 @@ The S3 API and the EFS API (for example) define possible error names. While the
We generate types for all defined shapes — including output shapes — but we don’t mashall the output SXML into appropriate Scheme values yet.
** Turn errors into Scheme conditions
This is easier said than done because different APIs return different kinds of errors.
+** TODO Respect “location” and “locationName”
+In the S3 API some values have a “location” property with value “header”, others with “querystring”. These values must appear in the headers or the querystring, respectively, and should not be added to the body.