Skip to content

Playground Feature: Improve the resource explorer #29

@psiemens

Description

@psiemens

👋   If you are interested in working on this issue, please check out the Getting Started guide on HackerEarth!

Problem

In the playground, the resource explorer is the tab the shows the resources inside each account. It is hidden initially and only shows up once you interact with an account's storage. But even then, it only shows up after you click an account, which usually decouples the view a transaction that updates the stored resources.

Furthermore, you can only see single account at once. If you want to view another account, you need to switch to it and probably lose the view, since second account doesn't have anything in its storage. Oops!

Example

Here we can see the resource explorer for account 0x02:

Screenshot from 2021-09-14 18-38-08

Account 0x03 doesn't have anything in its storage, so the view is not even rendered:

Screenshot from 2021-09-14 18-39-39

Solution

Create a better resource explorer! 😉

Here are some ideas for what you can do:

  • Build a way to quickly inspect multiple accounts.
  • Provide visual cues for different types of items in the storage(i.e. resources, capabilities, structs, etc). Maybe give them an icon, color, or both! 😎
  • Show the user who resources have been created or updated after a transaction is execute.
  • Autogenerate transaction or script templates for available capabilities, making it easier to write new interactions by simply clicking on a stored item and selecting the template.

Feel free to bring new ideas not listed above!

Experience Required

  • Great proficiency with TypeScript and React (front-end)
  • Good proficiency with GraphQL
  • Good proficiency with Go (back-end)
  • Good understanding of Cadence and its account and storage model
  • Good UX/UI design ability

Milestone Requirements

  1. Create wireframes for a new UI and interactions for the resource explorer.
  2. Implement an updated UI for resource explorer with current set of features.
  3. Add support for new features on both the frontend and backend.

Other Requirements

Code standards or guidelines

Design guidelines

  • New features should fit with the existing look and feel of the playground.

Judging Criteria

Resources

Metadata

Metadata

Assignees

Labels

Learning ToolsTier 2Medium task, spanning 2-3 milestones requiring a moderate level of domain knowledge.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions