Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expansion of features in the UI #466

Open
2 of 6 tasks
gabriel-indik opened this issue Dec 5, 2024 · 2 comments
Open
2 of 6 tasks

Expansion of features in the UI #466

gabriel-indik opened this issue Dec 5, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@gabriel-indik
Copy link
Contributor

gabriel-indik commented Dec 5, 2024

What would you like to be added?

Incorporate new features to the Paladin web based graphical user interface.

Why is this needed?

Currently the UI allows the user to explore transactions, submissions and registry entries. This can be expanded to to a larger feature set.

List of features

@gabriel-indik gabriel-indik added the enhancement New feature or request label Dec 5, 2024
@gabriel-indik
Copy link
Contributor Author

Current state of the UI

There are three main panels

Indexer

Screenshot 2024-12-05 at 10 17 30 AM Screenshot 2024-12-05 at 10 17 45 AM

Submissions

Screenshot 2024-12-05 at 10 17 55 AM Screenshot 2024-12-05 at 10 18 10 AM

Registry

Screenshot 2024-12-05 at 10 18 26 AM Screenshot 2024-12-05 at 10 18 48 AM

@gabriel-indik gabriel-indik self-assigned this Dec 5, 2024
@peterbroadhurst
Copy link
Contributor

peterbroadhurst commented Dec 6, 2024

This list is great @gabriel-indik.
Trying to fill out some detail on the requirements I see under each items, so maybe they can be split out to separate issues and prioritized... I'm putting them in rough prioritization here:

1. Navigating the complex data inside of a transaction receipt

  • The experience for "picking" a sub-transaction in an Atomic (4) one needs to give you some insight into which are which without picking one #470
    • Is the whole State Receipt available yes/no?
    • The Domain
  • We need to show you the details of the public transaction/events (there are APIs in Paladin for this)
    • For a transaction clicked on the left side
    • For an event clicked on the right side (currently this is just the event hex)

2 Simple key lookup

This folds under "network" (not keys) - you are asking for [email protected] here, so it's got to be clearly related to navigating the nodes.

3 ABI upload #468

  • The ability to paste/file-drop an ABI in
  • Deferrable: list of what ABIs have been uploaded
    • List of functions
    • List of events
    • List of errors
    • List of ABI-hashes (least useful)

4 Key management browsing

This is likely a whole new section of the experience that needs to be clear it's related to the local key management:

  • Navigation of keys in the something.nested.here path hierarchy
    • Direct lookup to a known fully qualified key
    • Nested navigation (like any folder/tree structure)
  • Reverse lookup of keys by verifier
    • With shortcut for Eth address
  • Displaying key information
    • The wallet a key is in
    • The list of verifiers that have been resolved for a key
      • With some priority on the eth address

5. Transaction debug

If a transaction is pending, let you grab the debug information for it.
This might be just JSON right now.

Added to the original list, as I think it fits here in the priority.

6. Network navigation

Added to the original list, as I think it fits here in the priority.

  • Reconciling the relationship between this and the "registry"
  • Listing currently connected nodes
  • Listing performed/queued state transfers to remote nodes

7. State Query

  • Build a UX around our JSON Query syntax (re-usable in many places)
  • Add a panel to use it to run queries against the state system

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants