search

tablelandnetwork / studio

Discover, design, deploy, and manage data driven web3 apps on Tableland.
https://studio.tableland.xyz
4 stars 1 forks source link

(cli) add chain and provider to `use` and add chain to init #174

Closed joewagner closed 9 months ago

joewagner commented 9 months ago

fixes https://linear.app/tableland/issue/STU-197/cli-creating-tables-or-importing-data-doesnt-use-login-context

This PR enables you to use "chain" and "provider", as well as adds the option to set a default chain value during the init command

railway-app[bot] commented 9 months ago

This PR was not deployed automatically as @joewagner does not have access to the Railway project.

In order to get automatic PR deploys, please add @joewagner to your team on Railway.

linear[bot] commented 9 months ago
STU-197 CLI: creating tables or importing data doesn't use `login` context

## Summary When I use `deployments create` or `import-data`, i *have to* pass the chain, providerUrl, and privateKey flags. However, I already logged in with these values, so i'd expect they would be used when i try to run these commands. ## Details Here's an example with `import-data`: ``` studio import-data test_table d.csv --pid de24e0a0-508c-4e1f-aa96-176a5ff2890a ``` When I do this, it will error out with `Error: invalid hexlify value`. If i pass the flags noted above, then it works. (I'm not sure if this is unexpected behavior or a UX consideration.)