[@kadena/graph-client] Added query information on each page

[MRVDH]

[changeset-bot]

🦋 Changeset detected

Latest commit: 6081855

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@kadena/graph-client	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

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

5 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
alpha-docs	⬜️ Ignored (Inspect)	Visit Preview		Jan 2, 2024 10:31am
docs-storybook	⬜️ Ignored (Inspect)	Visit Preview		Jan 2, 2024 10:31am
proof-of-us	⬜️ Ignored (Inspect)	Visit Preview		Jan 2, 2024 10:31am
react-ui	⬜️ Ignored (Inspect)	Visit Preview		Jan 2, 2024 10:31am
tools	⬜️ Ignored (Inspect)	Visit Preview		Jan 2, 2024 10:31am

[nil-amrutlal]

If there's more than one query with variables, does it still make sense to represent them in the same <DialogContent>? My concern is only if the variables happen to have the same name, it can be confusing to determine which one belongs to which.

[MRVDH]

Yep you're right. I have redone it to make more sense. Let me know what you think!

[nil-amrutlal]

Looks good 🙌🏽 just left a small comment. Also, maybe it would be nice to have it on the right side of the page? Just because I think its very close to the breadcrumbs. In any case, it is prob going to be changed again when we have a design so wouldn't bother too much with it

[MRVDH]

Looks good 🙌🏽 just left a small comment. Also, maybe it would be nice to have it on the right side of the page? Just because I think its very close to the breadcrumbs. In any case, it is prob going to be changed again when we have a design so wouldn't bother too much with it snip

Makes more sense indeed. Moved to the right!