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

Activity Log #132

Closed
8 tasks
wilwade opened this issue Feb 2, 2024 · 2 comments · Fixed by #153
Closed
8 tasks

Activity Log #132

wilwade opened this issue Feb 2, 2024 · 2 comments · Fixed by #153
Assignees

Comments

@wilwade
Copy link
Contributor

wilwade commented Feb 2, 2024

Image

  • Design from mocks
  • Data from "Current Transaction Status"
  • Show the blockhash under the log if there is one
  • Overflow should scroll
  • Newest event on top

dev details

  • Activity log store [array]
  • Keep tx status intact and we will evaluate at the end

nice to have

  • Nice to have: New events can be green or red text with a fade to normal over a few ms
@claireolmstead
Copy link
Contributor

Dev Notes:

@rlaferla
Copy link
Contributor

rlaferla commented Feb 6, 2024

With an event listener design, code is centralized to mostly if not entirely the ActivityLog component and connection status can be logged automatically. With a store design, each activity that needs to be logged has to be coded per component. Either design would work well but the event listener one may be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants