PLT-8891: Add marlowe-object contract flow example #136
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,18 @@ | ||
| { | ||
| "typescript.tsdk": "node_modules/typescript/lib", | ||
| "debug.javascript.terminalOptions": { | ||
| "outFiles": [ | ||
| "${workspaceFolder}/examples/nodejs/dist/**/*.js", | ||
| "${workspaceFolder}/packages/adapter/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/language/core/v1/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/language/examples/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/language/specification-client/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/token-metadata-client/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/wallet/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/runtime/client/rest/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/runtime/core/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/runtime/lifecycle/dist/esm/**/*.js", | ||
| "${workspaceFolder}/packages/marlowe-object/dist/esm/**/*.js" | ||
|
Comment on lines
+3
to
+15
There was a problem hiding this comment. The executed script has verified that the directories specified in the Analysis chainThe debug configuration for JavaScript has been added with specific Scripts ExecutedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Verify that the specified directories exist and contain .js files.
directories=(
"examples/nodejs/dist"
"packages/adapter/dist/esm"
"packages/language/core/v1/dist/esm"
"packages/language/examples/dist/esm"
"packages/language/specification-client/dist/esm"
"packages/token-metadata-client/dist/esm"
"packages/wallet/dist/esm"
"packages/runtime/client/rest/dist/esm"
"packages/runtime/core/dist/esm"
"packages/runtime/lifecycle/dist/esm"
"packages/marlowe-object/dist/esm"
)
for dir in "${directories[@]}"; do
if [ ! -d "$dir" ]; then
echo "Directory $dir does not exist."
elif [ -z "$(ls -A $dir/*.js)" ]; then
echo "No JavaScript files found in directory $dir."
else
echo "Directory $dir is correctly set up for debugging."
fi
done
Length of output: 2734 |
||
| ] | ||
| } | ||
| } | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
|
|
||
| ### General | ||
|
|
||
| - Feat: Added debugging configuration for VSCode. Now if you are developing with VSCode you can open the folder as a workspace and the [Javascript Debug Terminal](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_javascript-debug-terminal) will have the appropiate source maps. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)). | ||
|
There was a problem hiding this comment. Should debugging configuration really be included in the changelog? There was a problem hiding this comment. basically so you know this is now a thing (if not you wouldn't even have realized it) There was a problem hiding this comment. I wasn't able to make it work, if I can have 5 min of your time to do it @hrajchert ... once we have pushed our 2 PR for example... |
||
| - Feat: Started an experimental getApplicableActions that should replace the current getApplicableInputs. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
|
There was a problem hiding this comment. Are we officially using a convention for the change log ? like Feat, Breaking Change etc ? If yes it should be documented I guess, do we have some documentation around ? There was a problem hiding this comment. we discussed this together with you and @bjornkihlberg. But yes, we should/could document the structure |
||
|
|
||
| ### Examples | ||
| - Feat: Added a new interactive NodeJs example to make delayed payments with staking and merkleization. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
|
|
||
|
|
||
| ### @marlowe.io/adapter | ||
|
|
||
| - Feat: Added a bigint utilities adapter. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
| - Feat: Added iso8601ToPosixTime to the time adapter. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
|
|
||
| ### @marlowe.io/language-core-v1 | ||
|
|
||
| - Feat: Added SingleInputTx to capture a single step transaction (either a single input or an empty tx). ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)). | ||
| - Feat: Added getNextTimeout to see what is the next timeout of a contract. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)). | ||
| - Fix: Fix how merkleized inputs are serialized | ||
|
|
||
|
|
||
| ### @marlowe.io/runtime-rest-client | ||
|
|
||
| - [Breaking Change] Refactor: Create contract sources now uses a single parameter ContractBundle, instead of two separate bundle and main entrypoint parameters. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
| - [Breaking change] Fix: Pagination responses not always return a current header. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
|
|
||
| ### @marlowe.io/runtime-lifecycle | ||
|
|
||
| - Feat: Added restClient to the lifecycle object for easier querying. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
| - Feat: Added getInputHistory to get a list of SingleInputTx applied to a contract. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
|
|
||
| ### @marlowe.io/marlowe-object | ||
|
|
||
| - Feat: Added ContractBundle to represent a bundle with a main entrypoint. ([PR#136](https://github.com/input-output-hk/marlowe-ts-sdk/pull/136)) | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,3 @@ | ||
| [scriv] | ||
| format = md | ||
| categories = General, Examples, @marlowe.io/wallet, @marlowe.io/adapter, @marlowe.io/language-core-v1, @marlowe.io/language-examples, @marlowe.io/runtime-rest-client, @marlowe.io/runtime-core, @marlowe.io/runtime-lifecycle, @marlowe.io/language-examples, @marlowe.io/marlowe-object |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| *.config.json |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added this issue : #162 , because I'm not able to attach the debugger ti VSCode since we moved to packages, even with this PR, it doesn't work in my environment.