feat(studio, shinzohub): view pools - #302
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
shinzo-studio-internal | 2e3f803 | Commit Preview URL Branch Preview URL |
Jul 22 2026, 02:12 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
shinzo-studio | 2e3f803 | Commit Preview URL Branch Preview URL |
Jul 22 2026, 02:12 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
shinzo-explorer | 2e3f803 | Commit Preview URL Branch Preview URL |
Jul 22 2026, 02:12 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
shinzo-explorer-internal | 2e3f803 | Commit Preview URL Branch Preview URL |
Jul 22 2026, 02:13 PM |
| getNetworkUnitPrice, | ||
| listViewPools, | ||
| type ShinzoHubViewPool, | ||
| } from "@shinzo/shinzohub/views"; |
There was a problem hiding this comment.
[nit]: Can we use @shinzo/shinzohub for the import as we are doing before. the methods seems to be exported from @shinzo/shinzohub as well. This can be updated in the upcoming PRs as well.
johnnymatthews
left a comment
There was a problem hiding this comment.
Looks solid! The only (very minor) problem I encountered was that the View editor and preview fields highjack vertical scrolling. So if your cursor happens to be in one of them and you wanna move down, you can't.
In this video I use the central column to scroll down, move the cursor to the left, try to scroll, but can't. I do the same with the preview on the right.
Screen.Recording.2026-07-23.at.09.52.32.mov
Again, this is incredibly minor and likely something that most users won't notice. I also don't have a good/easy way to solve the issue. If you can think of something, it might be worth implementing? Otherwise, just leave this issue and ship!
|
Thanks for the feedback, @johnnymatthews and @NiranjanaBinoy! Already started implementing it in the follow-up PR. |
Closes #295
Two things here:
I tried to simplify the concepts of pools, demand, paid queries etc. That's why technical details live in their own hidden section, but the status is explained in simpler language.
Steps to Test