Skip to content

Explorer: Should the contracts route display the transaction component? #813

@telestrial

Description

@telestrial

Raised in a review of the Sia Central to explored transition for the contract route: how useful is the transaction data to the contract context?

Inputs and outputs feel unnecessary in this context. Better to link to the transaction page than muddying the context.

This is linking back to this page. Consider showing some revision metadata, like file size from each of the revisions instead

On the second bit of feedback, this likely expresses a UX improvement that would apply in several other places beyond the contract context, addressing: how can we keep users "grounded" as to where they're at in the blockchain? If they are presented a link that would take them to where they currently are, it would likely be valuable to indicate that. I could imagine a badge or indicator that says something like "Currently Viewing". Some version of a "You are here." It prevents (by perhaps not letting someone click through to where they already are) or at leasst flags the circular UI flow.

On the first comment, that's more complicated. We are currently displaying the transaction component with the data from the contract's transactionID, so small edits to this would be overrides to the transaction component (not a gigantic fan of that pattern) or a new component. Essential questions are:

  • Should this component be displayed at all?
  • If some amount of information in the transaction component is useful to the contract context, should we create a more slimmed down version of the component containing only that information?
  • Would a link to the transaction page be enough?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions