search

r0gue-io / pop-cli

An all-in-one tool for Polkadot development.
GNU General Public License v3.0
66 stars 19 forks source link

feat: integration with ui.use.ink #292

Open brunopgalvao opened 3 weeks ago

brunopgalvao commented 3 weeks ago

Currently when I deploy using Pop CLI, the deployed contract does not show up in ui.use.ink (or PolkadotJs Apps > Contracts).

As a developer, I need a way for when I deploy a contract using Pop CLI, that it shows up on the ui.use.ink because that UI is useful for debugging and part of the development process.

ui.use.ink is an invaluable tool in the smart contract development workflow

AlexD10S commented 2 weeks ago

Are you experimenting the same when deploying a smart contract using cargo-contract? This might need more research but seems more an issue of ui.use.ink that fails to show the contract.

brunopgalvao commented 2 weeks ago

Are you experimenting the same when deploying a smart contract using cargo-contract? This might need more research but seems more an issue of ui.use.ink that fails to show the contract.

Same. For both cases I have to go to ui.use.ink and manually add the code_hash of the deployed contract for the contract to show up in the UI.

AlexD10S commented 2 weeks ago

It seems like the issue might be on the ui.use.ink side, right? If the contract is deployed correctly on-chain, there’s probably not much we can address directly from the CLI.

brunopgalvao commented 2 weeks ago

It seems like the issue might be on the ui.use.ink side, right? If the contract is deployed correctly on-chain, there’s probably not much we can address directly from the CLI.

Yes, and it is critical to the success of Pop CLI smart contract development workflow.