-
When client is relying on certain version of API, and some “major” changes are introduced to the payload/error-handling, we need some versioning mechanism(uri/header) to prevent client failure
-
The way to set both the ledger and navigator port with `daml ledger navigator` is currently
```
daml ledger navigator --host localhost --port 6866 --port 4001
```
I'd prefer having different n…
-
Currently our JSON API performance tests focus on the performance of individual queries.
We should also test how performance is impacted by having ~300 concurrent users and which parameters in akka…
-
*Scenario:*
Ledger was running on sandbox classic with postgres, upgraded from 0.13.55 to 1.0.0 on sandbox classic.
`/v1/query` returning contract that has been archived before the upgrade. U…
-
When submitting a command to the ledger from the JSON API we should also include the template id and (for exercise/create-and-exercise) the choice name. Probably wouldn’t throw it in the context but i…
-
DABL's API is set up to provide unified JSON request/response as http-json project while providing some extra endpoints and different payloads for its own purposes. To ease the process of DABL ref…
-
A successful JSON API command submission will currently only produce a single log statement of the form
```
10:24:55.847 [http-json-ledger-api-akka.actor.default-dispatcher-5] INFO com.daml.http.Co…
-
Currently, values of DAML-LF variant types like
```
variant Foo =
| Bar Int
| Baz Foo.Baz
record Foo.Baz = {baz : Text}
```
get encoded to JSON values like
```json
{ "Bar": 5 }
{ "Baz": …
-
It would be nice if the result of a DAML choice would be exposed via the HTTP JSON API. In case people are worried about feature creep on the API, I want to give some arguments for why I think this ma…
-
This is a prerequisite to #11350 and #12689