Astar Treasury Proposal Roadmap - ink!DevHub 1.0 #218
Merged
Conversation
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
…191) In node install command, having version locking mechanism, and allow users specify which version to install with command args. Add command `swanky node version` --------- Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: prxgr4mm3r <berezan.ab@knu.ua>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
- created a new `env` command - moved the `check` functionality under `env` command - implemented an `install` command to install all or individual deps - added the *env* section to *swanky.config* on `init` with default version from docker base-image - implemented the edit flow for the *env* section in *swanky.config*
This PR are connected to [Ganache-like testing feature #49](inkdevhub/swanky-node#49). The main purpose of this issue is to make testing easier by implementing next features: > * block time stamp manipulation (can mine a block with arbitrary block time stamp) > * block number manipulation > * taking a snapshot and retrieve later > * Balance manipulation of accounts > * Impersonate any account All of them can already implemented in [Chopsticks](https://github.com/AcalaNetwork/chopsticks). Below I will explain how to use it. Firstly, you should set up your swanky project with `swanky init` and choose that you want to install swanky-node. Then you should use `swanky node chopsticks init` to initiate chopsticks config, which will be stored in the `./node/config/` folder. Then you start the node(`swanky node start`) and fork it with chopsticks(`swanky node chopsticks start`). Now we have a testing node that has all the features that we need. Chopsticks allow to use of different RPC calls. Full list of them you can check [here](https://acalanetwork.github.io/chopsticks/docs/chopsticks/README.html). For example, you can do timestamp manipulation by `dev_timeTravel' RPC call: ```TypeScript import { WsProvider } from '@polkadot/rpc-provider' const ws = new WsProvider(`ws://localhost:8000`) await ws.send('dev_timeTravel', ['Jan 1, 2023']) ``` Or go back to any block by 'dev_setHead': ```TypeScript import { WsProvider } from '@polkadot/rpc-provider' const ws = new WsProvider(`ws://localhost:8000`) await ws.send('dev_setHead', [1000000]) ``` --------- Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Added clear command and documentation.
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Redo normal merge after having rebase #205