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

[EPIC] Frontend support for 60min feeds #161

Closed
3 tasks done
trentmc opened this issue Sep 6, 2023 · 0 comments
Closed
3 tasks done

[EPIC] Frontend support for 60min feeds #161

trentmc opened this issue Sep 6, 2023 · 0 comments
Labels

Comments

@trentmc
Copy link
Member

trentmc commented Sep 6, 2023

About

Motivation + backend issue: pdr-backend#144

We need to support this in frontend too.

Towards a solution

One challenge: in the app, the table's header has labels that are specific for 5 min feeds. E.g. "13:55, 14:00, 14:05". This was done on purpose to help simplify the mental model.

  • We already discussed a solution: have a separate table for each time scale. Since we won't ever have that many timescales (e.g. 5 min, 60 min, 24h).
  • One possible implementation: Have all tables "tabbed". Each tab is right above the table header. There's a tab labeled "5m", another "60m", etc.

Requirements

  • Pre-requisite: pdr-backend supports 60-min feeds locally & on remote testnet (most of their work on pdr-backend 144)
  • Design: Implementation discussed and signed off. Tab-like solution to be implemented.

DoD:

  • Create 5m and 60m timeframe tabs
  • User is able to click between tabs to see all feeds
  • App refetches data and presents it to the user as required
@trentmc trentmc added the Type: Enhancement New feature or request label Sep 6, 2023
@trentmc trentmc added the Epic label Sep 6, 2023
@trentmc trentmc changed the title [EPIC] Full backend support for ten 60-minute feeds [EPIC] Frontend support for 60min feeds Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants