daml/compiler/daml-extension
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
..
images Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
snippets Simplify exercise snippet (#6232) 2020-06-04 22:17:10 +02:00
src Display why a party knows about a contract in table view (#6475) 2020-06-24 14:55:26 +00:00
syntaxes replace DAML Authors with DA in copyright headers (#5228) 2020-03-27 01:26:10 +01:00
test replace DAML Authors with DA in copyright headers (#5228) 2020-03-27 01:26:10 +01:00
.gitignore Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
.vscodeignore Fix VSCode extension (#2117) 2019-07-12 11:09:37 +02:00
BUILD.bazel tarball reproducibility (#5258) 2020-03-31 10:09:52 +02:00
ci-tests.sh replace DAML Authors with DA in copyright headers (#5228) 2020-03-27 01:26:10 +01:00
daml12.configuration.json Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
daml.configuration.json Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
exclude-list.txt Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
extension_guide.md Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
Makefile Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
package.json Fix vscode extension (#6379) 2020-06-17 13:17:48 +00:00
README.md Visual ide (#2467) 2019-08-12 12:42:45 -04:00
tsconfig.json Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
vsc-extension-quickstart.md Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
yarn.lock Fix vscode extension (#6379) 2020-06-17 13:17:48 +00:00

DAML Studio

DAML Studio extends Visual Studio Code with the following DAML-specific features:

  • DAML syntax highlighting
  • Real-time feedback on parse, name resolution, type-checking and Scenario interpretation errors and viewer for the resulting ledger
  • Jumping to and peeking at the definition of referenced toplevel functions
  • Type-information on hover
  • Renaming of symbols
  • DAML snippet support
  • Command to generate visualization for DAML project via command palette ctrl + p.

Please note that this will only install the VSCode extension. Full use of the above features will also require that you have a working DAML SDK installed, which you can get with:

curl -s https://get.daml.com | sh

To see graphs from daml.visualize command please install Graphivz plugin.

For more information on DAML please see docs.daml.com.

Troubleshooting

The DAML language server log output is available under the "Output" panel (View->Output). Select "DAML Language Server" from the dropdown in the panel to see the log.

Debugging

Run make then open this directory in Visual Studio Code. Then click Debug -> Start Debugging to run the extension in Debugging mode.