swanky-cli
swanky-cli copied to clipboard
inkdevhub
The all-in-one developer environment for Parity pallet-contracts based smart contracts!
At the moment, my `swanky.config.json` contains the following info for contracts: ```js "contracts": { "a_token": { "name": "a_token", "moduleName": "a_token", "deployments": [], "language": "ink", "build": { "timestamp": 1684712710067, "artifactsPath": "artifacts/a_token/1684712710067"...
# Overview (What and Why) Part of https://github.com/AstarNetwork/swanky-node/issues/49 swanky-node has manual block sealing feature via RPC `engine_createBlock` and `engine_finalizeBlock`. Allowing users to forward/finalize blocks manually using swanky-cli command or library...
# Overview (What and Why) We need to deploy a set of several smart contracts, x-compiled from Solidity to wasm, and maintain that deployment (deploy new contract instances and migrate...
# Overview (What and Why) New projects should have an (optional) CI pipeline added to them. Pipeline should compile and deploy the included contracts to swanky-node # How - [...
With v4, ink! now has e2e test support, which makes using mocha (node.js) redundant. If user choses ink! as a language, tests should be scaffolded using the ink! e2e framework....
When having dependency error, command should fail.
I propose renaming `init` command to `new`. There are two reasons for this that come to my mind: 1. Similarity with `cargo contract` -- it uses `new` for generating starting...
This fix: https://github.com/AstarNetwork/swanky-cli/issues/24 has caused some undesired behaviour (init command exits if yarn install fails, and doesn't create config file), so an additional param `shouldExitOnError` was added. Since there are...
When checking ink! version: https://github.com/AstarNetwork/swanky-cli/blob/f5789709931373dcad6b3c3f54668485c3020014/src/commands/check/index.ts#L119 `semver.gt()` errors out when `~` is used in the version tag. Could be gt() doesn't support the range operator, and it needs to be checked...
When checking the account, it should check the `isDev` flag. If true, it should prevent any `contract` subcommands on networks other than `local`. Enhancement: Allow adding `dev_` of `test_' prefix...