Display lab contract invoke url after deploy

[leighmcculloch]

The output of stellar contract deploy should display the URL for using lab to invoke the contract.

It would help direct the developer to the next step, and to be able to experience immediately.

It would help connect and discover related tools.

Existing deploy output as of today:

$ stellar contract deploy --wasm target/wasm32-unknown-unknown/release/soroban_increment_contract.wasm
ℹ️ Skipping install because wasm already installed
ℹ️ Using wasm hash aab6129c96013453bb697ddd8a67cbc57c97f8f950ade5840c0985e72c74be7b
ℹ️ Simulating deploy transaction…
ℹ️ Transaction hash is dba3738b2e9b9ff27dcfb747eea7ee656690db40ea6610dac922ecc1c86be70c
🔗 https://stellar.expert/explorer/testnet/tx/dba3738b2e9b9ff27dcfb747eea7ee656690db40ea6610dac922ecc1c86be70c
ℹ️ Signing transaction: dba3738b2e9b9ff27dcfb747eea7ee656690db40ea6610dac922ecc1c86be70c
🌎 Submitting deploy transaction…
🔗 https://stellar.expert/explorer/testnet/contract/CD64UAZLQ4Z6JPCVDCHOZANV7KP5MLFBOMGJV5T24GVMYZOH6SVC5OQN
✅ Deployed!
CD64UAZLQ4Z6JPCVDCHOZANV7KP5MLFBOMGJV5T24GVMYZOH6SVC5OQN

Proposed deploy output when deploying to testnet:

$ stellar contract deploy --wasm target/wasm32-unknown-unknown/release/soroban_increment_contract.wasm
ℹ️ Skipping install because wasm already installed
ℹ️ Using wasm hash aab6129c96013453bb697ddd8a67cbc57c97f8f950ade5840c0985e72c74be7b
ℹ️ Simulating deploy transaction…
ℹ️ Transaction hash is dba3738b2e9b9ff27dcfb747eea7ee656690db40ea6610dac922ecc1c86be70c
ℹ️ Signing transaction: dba3738b2e9b9ff27dcfb747eea7ee656690db40ea6610dac922ecc1c86be70c
🌎 Submitting deploy transaction…
🔗 https://lab.stellar.org/smart-contracts/contract-explorer/testnet/CD64UAZLQ4Z6JPCVDCHOZANV7KP5MLFBOMGJV5T24GVMYZOH6SVC5OQN
✅ Deployed!
CD64UAZLQ4Z6JPCVDCHOZANV7KP5MLFBOMGJV5T24GVMYZOH6SVC5OQN

Proposed deploy output when deploying to local:

$ stellar contract deploy --wasm target/wasm32-unknown-unknown/release/soroban_increment_contract.wasm
ℹ️ Skipping install because wasm already installed
ℹ️ Using wasm hash aab6129c96013453bb697ddd8a67cbc57c97f8f950ade5840c0985e72c74be7b
ℹ️ Simulating deploy transaction…
ℹ️ Transaction hash is dba3738b2e9b9ff27dcfb747eea7ee656690db40ea6610dac922ecc1c86be70c
ℹ️ Signing transaction: dba3738b2e9b9ff27dcfb747eea7ee656690db40ea6610dac922ecc1c86be70c
🌎 Submitting deploy transaction…
🔗 https://localhost:8000/lab/smart-contracts/contract-explorer/local/CD64UAZLQ4Z6JPCVDCHOZANV7KP5MLFBOMGJV5T24GVMYZOH6SVC5OQN
✅ Deployed!
CD64UAZLQ4Z6JPCVDCHOZANV7KP5MLFBOMGJV5T24GVMYZOH6SVC5OQN

Note that the above lab URLs also need adding to lab, so that lab will pickup those new URL formats.

[janewang]

@quietbits I think those URLs for Lab probably needs to carry some more data like network settings. What are your thoughts of also enable a link to Lab (in addition to stellar.expert). What's the right path for lab?

[fnando]

This is an easy change (I already have it in place), but the lab url pattern it not great, so you can't just cmd-click the link; you actually need to copy and paste the url in the browser, which makes it less useful.

We'd need to implement a redirect from /smart-contracts/contract-explorer?contractId=:contract_id to the proper url to be really useful.

🔗 https://lab.stellar.org/smart-contracts/contract-explorer?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&smartContracts$explorer$contractId=CCUHR3YCS53DW3GIKC5X7OK3IHRMTCCATBBHMMKDQGBZZEXLY25R3W7O;;

[fnando]

Implemented a redirect here: stellar/laboratory#1738