v0.12.24
0.12.24 - 2019-06-06
DAML Studio
- Fix errors due to unhandled
$/cancelRequest
andtextDocument/willSave
requests from showing up in the output tab in VSCode. These errors also caused an automatic switch from the problems tab to the output tab which should now no longer happen. - Note that upgrading the VSCode extension requires launching it via
daml studio
. If you launch VSCode directly, you might get issues due to an outdated extension.
0.12.23 - 2019-06-05
SQL Extractor
- 50MiB is no longer hard-coded on extractor input for sandbox or any other server, permitting large packages, e.g. pass
--ledger-api-inbound-message-size-max 62914560
to extractor to get a 60MiB limit. See #1520. - Improving logging. See #1518.
DAML Language
- BREAKING CHANGE: Contract key maintainers must now explicitly be computed from the contract key using the implicit
key
variable. For instance, if you havekey (bank, accountId) : (Party, Text)
and wantbank
to be the maintainer, you have to writemaintainer key._1
(before, you could writemaintainer bank
).
DAML Compiler
-
BREAKING CHANGE: Drop support for DAML-LF 1.3. Compiling to DAML-LF 1.4 should work without any code changes, although we highly recommend not specifying a target DAML-LF version at all. (The ledger server still supports DAML-LF 1.3.)
-
Fix initialization of package-db for non-default DAML-LF versions. This fixes issues when using
daml build --target 1.3
(or other target versions).
DAML Standard Library
- Add
enumerate
function.
Navigator
- Fixed a regression where Navigator console was not able to inspect contracts and events. See #1454.
- 50MiB is no longer hard-coded on extractor input for sandbox or any other server, permitting large packages, e.g. pass
--ledger-api-inbound-message-size-max 62914560
to extractor to get a 60MiB limit. See #1520.
Sandbox
- Added recovery around failing ledger entry persistence queries using Postgres. See #1505.