Skip to content
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

feat: integration with ui.use.ink #292

Open
brunopgalvao opened this issue Aug 22, 2024 · 4 comments
Open

feat: integration with ui.use.ink #292

brunopgalvao opened this issue Aug 22, 2024 · 4 comments
Labels
contracts Features related to smart contracts enhancement New feature or request

Comments

@brunopgalvao
Copy link
Collaborator

brunopgalvao commented Aug 22, 2024

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

@brunopgalvao brunopgalvao added enhancement New feature or request contracts Features related to smart contracts labels Aug 22, 2024
@brunopgalvao brunopgalvao changed the title feat: integration with [ui.use.ink](https://ui.use.ink) feat: integration with ui.use.ink Aug 22, 2024
@AlexD10S
Copy link
Collaborator

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
Copy link
Collaborator Author

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
Copy link
Collaborator

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
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contracts Features related to smart contracts enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants