daml/triggers
Stephen Compall 664a0c0076
add Action to high-level trigger updateState (#7621)
* add ActionState to the standard library

* use 1 ActionState, 1 get, 1 put in low-level trigger library

* introduce TriggerStateA for updateState

* fix tests and examples for new updateState signature

CHANGELOG_BEGIN
- [Triggers] The ``updateState`` function now returns a ``TriggerStateA``.  This
  is an action like ``TriggerA``, but doesn't permit emitting commands.  Instead
  of taking the state as an argument and returning a new state, you can
  manipulate the state with ``get``, ``put``, and ``modify``.  Any existing
  ``updateState`` can be ported by replacing ``s -> expr`` in the lambda
  expression with ``-> modify $ \s ->``, and then made to look nicer from there
  as desired.
  See `issue #7621 <https://github.com/digital-asset/daml/pull/7621>`__.
CHANGELOG_END

* some DAML docs for updateState and TriggerStateA
2020-10-09 13:56:24 -04:00
..
daml add Action to high-level trigger updateState (#7621) 2020-10-09 13:56:24 -04:00
runner remove known command ID from trigger state once Transaction and Completion message are seen (#7598) 2020-10-07 18:32:49 +00:00
service add Action to high-level trigger updateState (#7621) 2020-10-09 13:56:24 -04:00
tests add Action to high-level trigger updateState (#7621) 2020-10-09 13:56:24 -04:00