No parties in create-daml-app's daml.yaml template, (digital-asset#12952

) ... so that Navigator shows users for login by default. When parties are specified explicitly in daml.yaml, navigator uses those instead of querying user management for the list of users a user can log in as. These days, it actually doesn't make sense to list the parties in the daml.yaml. Navigator will query party mgmt for a list of known parties. We don't implicitly allocate parties (anymore), so unclear why this section is still here. The users for the template are created by the init script (see Setup.daml). See digital-asset#12945 CHANGELOG_BEGIN CHANGELOG_END
TuranDev · Feb 15, 2022 · 612bf97 · 612bf97
1 parent f3af828
commit 612bf97
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 8 deletions.
diff --git a/templates/create-daml-app/daml.yaml.template b/templates/create-daml-app/daml.yaml.template
@@ -2,10 +2,6 @@ sdk-version: __VERSION__
 name: __PROJECT_NAME__
 version: 0.1.0
 source: daml
-parties:
-- Alice
-- Bob
-- Charlie
 dependencies:
 - daml-prim
 - daml-stdlib

diff --git a/templates/gsg-trigger.patch b/templates/gsg-trigger.patch
@@ -85,10 +85,10 @@ diff --git create-daml-app/daml/User.daml create-daml-app/daml/User.daml
 +-- MESSAGE_END
 --- create-daml-app/daml.yaml.template	2022-01-26 17:29:37.149557361 +0100
 +++ create-daml-app/daml.yaml.template	2022-01-26 17:29:27.749276386 +0100
-@@ -6,10 +6,12 @@
- - Alice
- - Bob
- - Charlie
+@@ -2,10 +2,12 @@
+ name: __PROJECT_NAME__
+ version: 0.1.0
+ source: daml
 +# trigger-dependencies-begin
  dependencies:
  - daml-prim