daml/compiler/daml-extension
Anup Kalburgi 09b766c502 Visual integration with LSP (#2597)
* daml visualize with lsp

* Working command execution with ide

* Have to call visual now

* Split function

* Wrong constuctions of world or the module

* Working almost

* Have to gather all modules

* Now works end to end. Considers all the daml files in workspace

* removing unused code

* removing unused dependency

* Removing unused JS code and better error message

* Function re-arrange

* Removing us of heaad, instead handling error

* Format and rearranging

* Removing unused assignment

* Formating everything

* missed dependency

* Generating visual only for the file that is open

* Using modules from generated pkg, error messages

* Bringing back the commands

* Names and formating

* consitent error message

* Removing Just pattern match using _use now

* package

* Moving visual to a different module

* Function simple

* Removing Rule as it increases memeory consumption

* TODO LSP error

* White space

* Fmt things

* Handling if command was executed for a non daml files

* Better error message

* debugging

* Fix executeCommand

* Adding tests to execute command. Thanks moritz

* Unwanted lines

* Spaces and comment

* 3rd time ?

* Spaces are white

* assert equal instead of assert bool
2019-08-26 15:47:29 +00:00
..
images Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
snippets Move code in daml-tools outside of daml-foundations (#2033) 2019-07-08 11:40:48 +02:00
src Visual integration with LSP (#2597) 2019-08-26 15:47:29 +00:00
syntaxes Stop highlighting signature as a keyword in the IDE (#2599) 2019-08-20 07:23:39 +00:00
test update copyright notices (#2499) 2019-08-13 17:23:03 +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 update copyright notices (#2499) 2019-08-13 17:23:03 +01:00
ci-tests.sh update copyright notices (#2499) 2019-08-13 17:23:03 +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 Visual integration with LSP (#2597) 2019-08-26 15:47:29 +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 Visual ide (#2467) 2019-08-12 12:42:45 -04: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.