mirror of
https://github.com/digital-asset/daml.git
synced 2024-10-26 05:09:36 +03:00
f8c0a35940
* rewrite trigger docs to follow gsg Per #10419 point 4, I've rewritten the Triggers section to build upon the Getting Started Guide instead of inventing its own example. Compared to #10395, this has a lot more explanations as this page must now serve the dual purpose of being a possible "next step" from the GSG and being the main reference page for triggers. It's also lost the "next steps" section, which I think is a bit of a shame, but it doesn't really make sense here. There's also no easy way for people not interested in the GSG to follow along; should we expose the "completed GSG" as a tempate? CHANGELOG_BEGIN CHANGELOG_END * keep copy-trigger as a template * fix copy-trigger project name * make up gsg-trigger template * remove awkward sentence, fix existing typo * update code to use when{,Some} * add to * swap emitCommands and getCommandsInFlight * typo * insist on state-correction perspective * fix copy-trigger tests * add back copy-trigger to whitelist * add gsg-trigger to whitelist |
||
---|---|---|
.. | ||
copy-trigger | ||
create-daml-app | ||
create-daml-app-test-resources | ||
empty-skeleton | ||
quickstart-java | ||
quickstart-scala | ||
skeleton | ||
BUILD.bazel | ||
default-dlint.yaml | ||
default-gitattributes | ||
default-gitignore | ||
gsg-trigger.patch | ||
NO_AUTO_COPYRIGHT | ||
README.txt |
These are template projects for `daml new`. Testing the create-daml-app template ==================================== While automated integration tests for the create-daml-app template are being built, we have the following manual testing procedure. Note that this is for testing against the head of the daml repo. For testing against a released SDK, you can skip past the package.json step and use `daml` instead of `daml-head` after installing the released version. First, build the SDK from head using the `daml-sdk-head` command. This gives an executable Daml assistant called `daml-head` in your path. Next, instantiate the `create-daml-app` template as follows: ``` daml-head new create-daml-app --template create-daml-app cd create-daml-app ``` Crucially, you'll need to add a package.json file at the root of the project for testing (this is not required when using the released SDK). It should look as follows, with the dummy paths here replaced by relative paths to locally built TypeScript libraries. (These need to be built from head using Bazel: ``` bazel build //language-support/ts/daml-types bazel build //language-support/ts/daml-ledger bazel build //language-support/ts/daml-react```) package.json: { "resolutions": { "@daml/types": "file:path/to/daml-types/npm_package", "@daml/ledger": "file:path/to/daml-ledger/npm_package", "@daml/react": "file:path/to/daml-react/npm_package" }, "private": true, "workspaces": [ "daml.js", "ui" ] } Now you can continue to build and run the project as described in create-daml-app/README.md, using `daml-head` instead of `daml`. Specifically, you should run the following in the root directory: ``` daml-head build daml-head codegen js .daml/dist/create-daml-app-0.1.0.dar -o daml.js daml-head start ``` Then in another terminal, navigate to `create-daml-app/ui/` and run: ``` yarn install yarn start ``` And check that the app works. Finally, terminate both the `daml start` and `yarn start` processes and run `yarn test` from the `ui` directory. All tests should pass.