-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mention peregrine in quickstart guide #262
Conversation
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
||
<Tabs groupId="ts-js-choice"> | ||
<TabItem value='ts' label='Typescript' default> | ||
|
||
From inside the `kilt-rocks` project directory, install the **KILT SDK**, **Ts-node**, **Axios** and **Typescript**: | ||
From inside the `kilt-rocks` project directory, install the **KILT SDK**, **Typescript**, **ts-node** and **Axios**: |
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.
Should we then also change the order of the installation in the npm install
command below?
</SnippetBlock> | ||
|
||
After establishing a connection, you have access to the chain, but let's not forget to **close** any connections when we are done! | ||
Connections to blockchain nodes should be dropped when no longer needed: to do that simply call the `Kilt.disconnect()` function at the bottom of `main` function. | ||
By adding `await Kilt.disconnect()` at the end of the main function, you ensure that the connection to the blockchain node is properly closed when the script finishes executing. |
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.
By adding `await Kilt.disconnect()` at the end of the main function, you ensure that the connection to the blockchain node is properly closed when the script finishes executing. | |
By adding `await Kilt.disconnect()` at the end of the main function, you ensure that the connection to the blockchain node is properly closed when the script terminates execution. |
After establishing a connection, you have access to the chain, but let's not forget to **close** any connections when we are done! | ||
Connections to blockchain nodes should be dropped when no longer needed: to do that simply call the `Kilt.disconnect()` function at the bottom of `main` function. | ||
By adding `await Kilt.disconnect()` at the end of the main function, you ensure that the connection to the blockchain node is properly closed when the script finishes executing. | ||
This helps maintain the integrity of your application and is a good practice to follow. |
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.
What does integrity means?
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.
keeping the app state free from resource leaks which could lead to a crash. Integrity as in an unimpaired condition
docs/develop/01_sdk/01_quickstart.md
Outdated
You have connected to a Spiritnet node. | ||
Let's now start querying some data from the chain!** | ||
Congratulations! | ||
You have connected to a blockchain node. |
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.
maybe?
You have connected to a blockchain node. | |
You have connected to a KILT blockchain node. |
fixes https://github.com/KILTprotocol/ticket/issues/2674