-
Notifications
You must be signed in to change notification settings - Fork 307
feat(dev-hub) Pyth Pro pages Part-1 #3191
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
5 Skipped Deployments
|
| { id: "description", name: "Description" }, | ||
| { id: "name", name: "Name" }, | ||
| { id: "symbol", name: "Symbol" }, | ||
| { id: "pyth_lazer_id", name: "Pyth Pro ID", isRowHeader: true }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit maybe ux wise if this is going to be sorted by it should be the first column in the table?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about it before. Since the pyth_pro_id starts from 1 and sequentially incremented, it can confused with the index. Sicne folks try to read the symbol and description and then refer to the pro_id, it would be better we keep it on the right side.
Summary
Rationale
How has this been tested?