-
Notifications
You must be signed in to change notification settings - Fork 9
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
Vertical blocks #205
Vertical blocks #205
Conversation
43b8b06
to
fd01eb7
Compare
3b27cda
to
a37a166
Compare
df53498
to
c967245
Compare
<Box>{children}</Box> | ||
|
||
{action} |
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.
This is an odd place to put it. Mobile search floats above anyway right, so can't the button simply be in the footer, next to Typography?
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.
Didn't found any smart solution to place the button in the center.
src/app/pages/BlocksPage/index.tsx
Outdated
{tableView === TableView.Vertical && ( | ||
<BlockDetails> |
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.
It bothers me that these vertical cards aren't just a different layout of a table. They are a complete second implementation of Blocks list and of Transactions list. It doubles complexity of every view that supports it.
Some limitations if it was implemented as a Table feature instead (converting columns into rows):
- Cards would have to show the same information as the table shows. No new information like transaction's
Gas limit
that is not a column - And show it in the same order as columns are
- Pagination
- It would still have to leak implementation details into parent queries (limit, offset)
Show More
could not be part of the footer
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.
Right, I agree it could have been done more general. But Didn't wan't to complicate the Table component. I suggest we keep it as is, and refactor, if we add the 3th view.
90d47ec
to
9c17401
Compare
3b4337b
to
c438c76
Compare
c438c76
to
e4479ca
Compare
2115987
to
5b2e794
Compare
4e0fae3
to
92fd028
Compare
8ae2aba
to
1fb6b34
Compare
Solution
Implement vertical view on blocks and transactions page
Links
https://www.loom.com/share/b816268e56ba4851b90509e4415d4696