Martin Huschenbett c4cd51389e Display why a party knows about a contract in table view (#6475) ... * Display why a party knows about a contract in table view When displaying scenario results in table view in DAML Studio, we now indicate _why_ a party knows about the existence of a contract: - `S` means the party is a signatory. - `O` means the party is an observer. - `D` means the party has learned about the contract via disclosure or divulgence. With the information we get from the scenario service there is no straightforward way of distinguishing between disclosed (you witnessed the `create`) and divulged (you witnessed a `fetch`) contracts. Fortunately, both words start with a "D" and we're fine. :) This addresses the first point of https://github.com/digital-asset/daml/issues/6412 for the table view. CHANGELOG_BEGIN * [DAML Studio] When displaying scenario results in table view in DAML Studio, we now indicate _why_ a party knows about the existence of a contract: - `S` means the party is a signatory. - `O` means the party is an observer. - `D` means the party has learned about the contract via disclosure or divulgence. CHANGELOG_END * Add tooltips CHANGELOG_BEGIN CHANGELOG_END * Add test CHANGELOG_BEGIN CHANGELOG_END * Remove tooltip for invisible contracts CHANGELOG_BEGIN CHANGELOG_END * Move parties to then end CHANGELOG_BEGIN CHANGELOG_END		2020-06-24 14:55:26 +00:00
..
src/DA/Daml/LF	Display why a party knows about a contract in table view (#6475)	2020-06-24 14:55:26 +00:00
BUILD.bazel	Move GHC session to a Shake rule (#5517)	2020-04-09 17:11:40 +02:00