mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
05505e3d03
* Initial work-in-progress changelog_begin [TS bindings] When using daml-react and daml-ledger, all streaming request to the query endpoint will be multiplexed through a single web socket. changelog_end * Minor touches, renaming * Handle offsets received from the JSON API * Create state array once per downstream consumer * Handle reconnections as streamSubmit does * Don't share mutable state between events * Fix compilation errors * Remove language-support/ts/package-lock.json * Remove --downlevelIteration option, materialize iterators, fix one test * I will refrain from commenting on the meaning of `this` in JavaScript * WebSocket does not have a removeAllListeners method * Remove unnecessary docstring from `handleQueriesChange` * Address https://github.com/digital-asset/daml/pull/10221#discussion_r670441680 * Address https://github.com/digital-asset/daml/pull/10221#discussion_r670427941 * Address https://github.com/digital-asset/daml/pull/10221#discussion_r670448474 * Address https://github.com/digital-asset/daml/pull/10221#discussion_r670473307 * Fix some failing tests and linting fixes * fix reconnect on server close test * fix failing tests in test.ts and create-daml-app tests * Update language-support/ts/daml-ledger/index.ts Co-authored-by: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * Update language-support/ts/daml-ledger/index.ts Co-authored-by: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * Update language-support/ts/daml-ledger/index.test.ts Co-authored-by: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * Update language-support/ts/daml-ledger/index.test.ts Co-authored-by: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * changes based on code review comments Co-authored-by: Akshay <akshay.shirahatti@digitalasset.com> Co-authored-by: akshayshirahatti-da <86774832+akshayshirahatti-da@users.noreply.github.com> |
||
---|---|---|
.. | ||
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.