Enable DAML Script service by default and document it (#7229)

* Enable DAML Script service by default and document it

fixes #7193

changelog_begin

- [DAML Script] DAML Scripts are now run in DAML Studio just like
  scenarios. The functionality for inspecting the results is
  identical. If you encounter issues, please report them.

changelog_end

* fix double "is identical"

changelog_begin
changelog_end

Author: cocreature

compiler/damlc/lib/DA/Cli/Options.hs

@@ -209,7 +209,7 @@ enableScenarioOpt = EnableScenarioService <$>
 
 enableScriptsOpt :: Parser EnableScripts
 enableScriptsOpt = EnableScripts <$>
-    flagYesNoAuto "daml-script" False "Enable/disable support for running DAML Scripts" internal
+    flagYesNoAuto "daml-script" True "Enable/disable support for running DAML Scripts" internal
 
 dlintEnabledOpt :: Parser DlintUsage
 dlintEnabledOpt = DlintEnabled

compiler/lsp-tests/src/Main.hs

@@ -542,7 +542,7 @@ scriptTests damlcPath scriptDarPath = testGroup "scripts"
             , "- daml-script.dar"
             ]
         withCurrentDirectory dir $
-            runSessionWithConfig conf (damlcPath <> " ide --daml-script=yes") fullCaps' dir s
+            runSessionWithConfig conf (damlcPath <> " ide") fullCaps' dir s
 
 executeCommandTests :: (forall a. Session a -> IO a) -> (Session () -> IO ()) -> TestTree
 executeCommandTests run _ = testGroup "execute command"

docs/source/daml-script/index.rst

@@ -15,13 +15,14 @@ in a special process and do not interact with an actual ledger. This
 means that you cannot use scenarios to test other ledger clients,
 e.g., your UI or :doc:`DAML triggers </triggers/index>`.
 
-DAML script addresses this problem by providing you with an API with
+DAML Script addresses this problem by providing you with an API with
 the simplicity of DAML scenarios and all the benefits such as being
-able to reuse your DAML types and logic while running against an
-actual ledger. This means that you can use it to test automation
-logic, your UI but also for
-:ref:`ledger initialization <script-ledger-initialization>` where scenarios
-cannot be used (with the exception of :doc:`/tools/sandbox`).
+able to reuse your DAML types and logic while running against an actual
+ledger in addition to allowing you to experiment in :ref:`DAML Studio <scenario-results>`.
+This means that you can use it to test automation logic, your
+UI but also for :ref:`ledger initialization
+<script-ledger-initialization>` where scenarios cannot be used (with
+the exception of :doc:`/tools/sandbox`).
 
 You can also use DAML Script interactively using :doc:`/daml-repl/index`.
 

docs/source/daml/daml-studio.rst

@@ -97,12 +97,17 @@ You can `hover`_ over most symbols in the code to display additional information
 
 .. _hover: https://code.visualstudio.com/docs/editor/editingevolved#_hover
 
-Scenario results
-================
+.. _scenario-results:
 
-Top-level declarations of type ``Scenario`` are decorated with a ``Scenario results`` code lens.
-You can click on the ``Scenario results`` code lens to inspect the
-execution of the scenario.
+Scenario and DAML Script results
+================================
+
+Top-level declarations of type ``Scenario`` or ``Script`` are decorated with
+a ``Scenario results`` or a ``Script results`` code lens.
+You can click on the code lens to inspect the
+execution transaction graph and the active contracts. The functionality
+for inspecting the results is identical for DAML Scripts
+and scenarios.
 
 For the scenario from the :download:`Iou<daml-studio/daml/Iou.daml>`
 module, you get the following table displaying all contracts that are