Releases: digital-asset/daml
v0.12.15
0.12.15 - 2019-05-06
-
Windows support: Beta release of the Windows SDK.
To try it out, download the installer from GitHub releases. The Windows SDK uses the new
daml
command-line which will soon also
become the default on Linux and MacOS.Documentation is still in progress, but you can see the Migration guide and the pull request for the updated documentation.
-
DAML Standard Library: Added
fromListWith
andmerge
toDA.TextMap
. -
DAML Standard Library: Deprecated
DA.Map
andDA.Set
. Use the newDA.Next.Map
andDA.Next.Set
instead. -
Ledger API: Added three new methods to the :ref:
CommandService <com.digitalasset.ledger.api.v1.commandservice>
:SubmitAndWaitForTransactionId
returns the transaction ID.SubmitAndWaitForTransaction
returns the transaction.SubmitAndWaitForTransactionTree
returns the transaction tree.
-
Ledger API: Added field
transaction_id
to command completions. This field is only set when a command is successful. -
DAML Standard Library: Added instances of
Functor
,Applicative
, andAction
for(->) r
(the reader monad).
0.12.14 - 2019-05-03
- DAML Standard Library: The
id
function was previously deprecated and has now been removed. Useidentity
instead. - DAML and Assistant: The compiler no longer supports DAML-LF 1.0.
- DAML-LF: As a new "dev" minor version, writing with
--target 1.dev
is now supported by all tools by default. - Ledger API: You can now look up flat transactions with the new TransactionService methods
GetFlatTransactionByEventId
andGetFlatTransactionById
.
0.12.13 - 2019-05-02
- Fix an issue with Postgres of potentially not stopping the transaction stream at required ceiling offset. See more here
v0.12.12: Release 0.12.12 (#792)
0.12.12 - 2019-04-30
- Sandbox: Added support for using a Postgres database as a back end for the Sandbox, which gives you persistent data storage. To try it out, see tools/sandbox
- DAML Integration Kit: Added documentation for /daml-integration-kit/index. The docs explain what the DAML Integration Kit is, what state it is in, and how it is going to evolve.
- DAML Integration Kit: Released the Ledger API Test Tool. To try it out, see /tools/ledger-api-test-tool/index.
- DAML-LF: Removed DAML-LF Dev major version, --target dev option, and sandbox --allow-dev option.
- A "1.dev" target will handle the intended "Dev" use cases in a future release.
- Ledger API: The list of DAML packages used during interpretation is now included in the produced transaction.
- Scala: Source JARs are now released for Scala libraries.
- DAML Standard Library: Renamed DA.TextMap.filter and DA.Map.filter to filterWithKey.
- Contract keys: Fixed bug related to visibility and contract keys. For details, see issue #751.
- Contract keys: Fixed bug related witness parties in transaction events. For details, see issue #794.
v0.12.11: Release 0.12.11 (#713)
0.12.11 - 2019-04-26
- Node.js bindings have been moved here.
- Add documentation for flexible controllers.
0.12.10 — 2019-04-25
- Make DAML-LF 1.3 the default compilation target for the DAML compiler. This means that contract keys and text maps are now available by default in DAML.
0.12.9 — 2019-04-23
- Addition of
DA.Math
library containing exponentiation, logarithms and trig functions - Add CreateAndExerciseCommand to Ledger API and DAMLe for creating a contract and exercising a choice on it within the same transaction. This can be used to implement "callable updates" (aka functions of type
Update a
that can be called from the Ledger API via a contract). - Publish the participant-state APIs and reference implementations.
- Add
-s
option to Sandbox CLI to have a shortened version for--static-time
as well - Change
--allow-dev
to be a hidden CLI option in Sandbox
0.12.7 — 2019-04-17
- Fix release pipeline (hopefully)
0.12.6 — 2019-04-16
- RxJava Bindings: remove blocking call inside Bot.wire, which could lead to an application not making progress in certain situations.
0.12.5 — 2019-04-15
- Fix release pipeline (hopefully)
- DAML-LF Archive packaging: the DAML-LF Archive Protobuf definitions are now packaged so that it's possible to use them without mangling the path.
0.12.4 — 2019-04-15
v0.12.3
0.12.3 — 2019-04-12
- Fix navigator and extractor packaging in the SDK.
0.12.2 — 2019-04-12
- Add flexible controllers and disjunction choices to DAML.
- Introduce experimental support for using Postgres as a backend for the Sandbox. The optional CLI argument for it named
--jdbcurl
is still hidden. - Node.js Bindings: fix validation for Ledger API timestamp values.
- Node.js Bindings: drop support for identifier names, replacing them with separated module and entity names.
- Node.js Bindings: use strings instead of numbers to represent Ledger API timestamps and dates.
- Node.js Bindings: use strings instead of numbers to represent Protobuf 64-bit precision integers to avoid a loss of precision.
- Java Codegen: support DAML TextMap primitive which is mapped to
java.util.Map
type with keys restricted tojava.lang.String
instances. - Java Codegen: leaner log output.
- Java Codegen: add flag for log verbosity:
-V LEVEL
or--verbosity LEVEL
, whereLEVEL
is a number between0
(least verbose) and4
(most verbose). - BREAKING Remove support for DAML 1.0 packages in the engine, and thus the sandbox. Note that the SDK has removed support for compiling DAML 1.0 months ago.
0.12.1 — 2019-04-04
- Fix release process
0.12.0 — 2019-04-04
-
Change in how values are addressed in Navigator's
frontend-config.js
.-
Old syntax for accessing values:
argument.foo.bar
-
New syntax:
import { DamlLfValue } from '@da/ui-core'; // Accessing field 'bar' of field 'foo' of the argument DamlLfValue.evalPath(argument, ["foo", "bar"]) DamlLfValue.toJSON(argument).foo.bar
-