daml/language-support/scala/bindings-akka
Stephen Compall bafde51752
add silent_annotations option to da_scala bazel functions (#7668)
* add silent_annotations option to da scala bazel functions

* use silent_annotations for several scala targets

* use silencer_plugin instead when the lib isn't used

* use silent_annotations for several more scala targets

* use silencer_lib for strange indirect requirement for running tests

* no changelog

CHANGELOG_BEGIN
CHANGELOG_END

* silent_annotations support for scaladoc
2020-10-13 15:44:16 +00:00
..
src use -Ywarn-unused for all Scala code (#6907) 2020-08-07 13:16:09 -04:00
BUILD.bazel add silent_annotations option to da_scala bazel functions (#7668) 2020-10-13 15:44:16 +00:00
README.md open-sourcing daml 2019-04-04 09:33:38 +01:00

Ledger Client Binding

This module contains the glue code between nanobot-framework, scala-codegen and prototype-client (Scala binding for the ledger API). The gRPC API provided by prototype-client as it is is not type-safe. The incomming Transactions from LedgerClient is routed to DomainTransactionMapper, which will:

  • convert the data in Transaction to type-safe types coming from api-refinements
  • call the EventDecoder provided by scala-codegen for created events
  • verify that the messages contain all the neccessary fields, and remove Optional wrappers

The result of this will be the Domain* classes.

In the other directions (for the commands coming out from the nanobots) the 'CompositeCommandAdapter' will be used to transform back to the gRPC interface (SubmitRequest). After the command submission, the outcoming Completion will be used to check the result, and based on that the CommandRetryFlow can decide wether the command should be retried or an error should be reported.