Use/import table

[asutula]

The new feature here is a popover menu on the tableland table page/deployment page that allows the user to import the table into an existing project or use the table schema in a new table within a project.

This led to upgrades to trpc and iron-session, which caused lots of files to be touched.

I commented on every file with changes worth knowing about and reviewing. If a file has no comments, it's because the changes were already discussed in a previous file (usually just some naming change or api usage refactor), so you can breeze past those.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 30, 2024 2:22am

[railway-app[bot]]

This PR is being deployed to Railway 🚅

web: ◻️ REMOVED

[asutula]

@joewagner I'm having trouble understanding why/where the tests are failing. Let me know if you can tell.

[asutula]

@joewagner I'm having trouble understanding why/where the tests are failing. Let me know if you can tell.

Oh I see some needed updates that need to be made to the tests. Trying now...

[joewagner]

Below is a screen grab of the slide out when importing a an existing table.

I'm confused why there is an option to select chain id and table id. If you're importing a table doesn't that mean that you would be using an existing tableland table in a project?

[joewagner]

I found what might be an existing bug: If I import tables into a project, then I go to the project page via the normal navigation links, I don't see any of the tables. When I do a hard refresh on the page the imported tables are in the project.

[joewagner]

I found what might be an existing bug: If I import tables into a project, then I go to the project page via the normal navigation links, I don't see any of the tables. When I do a hard refresh on the page the imported tables are in the project.

I can confirm this issue does not exist on production, but the same thing happens when I import a schema.

[asutula]

Will try to reproduce those bugs @joewagner, thanks.

[asutula]

Below is a screen grab of the slide out when importing a an existing table.

I'm confused why there is an option to select chain id and table id. If you're importing a table doesn't that mean that you would be using an existing tableland table in a project?

Yea, we preset those fields to the correct values, we could go an additional step and make them non editable?

[asutula]

I found what might be an existing bug: If I import tables into a project, then I go to the project page via the normal navigation links, I don't see any of the tables. When I do a hard refresh on the page the imported tables are in the project.

Fixed. Good catch.

[asutula]

I found what might be an existing bug: If I import tables into a project, then I go to the project page via the normal navigation links, I don't see any of the tables. When I do a hard refresh on the page the imported tables are in the project.

I can confirm this issue does not exist on production, but the same thing happens when I import a schema.

Also fixed.

[asutula]

Below is a screen grab of the slide out when importing a an existing table. I'm confused why there is an option to select chain id and table id. If you're importing a table doesn't that mean that you would be using an existing tableland table in a project?

Yea, we preset those fields to the correct values, we could go an additional step and make them non editable?

Went ahead and disabled those form inputs if chain and table id presets are provided.

[asutula]

Note: @joewagner this branch was just rebased and then force-pushed to origin.

[asutula]

Ok, I think all feedback so far has been addressed. Looking good with the new theme too.