-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: Consider using feat view related utility classnames #519
feat: Consider using feat view related utility classnames #519
Conversation
Deployed to https://pr-519-aescan.stg.aepps.com |
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.
Massive improvement!! Well done, code-wise looks great but we will need some help from Liubov to verify if there are no regressions.
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.
Great job! Please have a look at my comment.
.token-holders-panel { | ||
&__table { | ||
display: none; | ||
margin-bottom: var(--space-4); |
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.
margin-bottom: var(--space-4);
got removed. Can you check it?
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.
Nope, for this case was not needed. Forgot to comment this
Description
resolves #93
I think it was a good time to use utility classes. I am not against utility classes, but should be used as a syntactic sugar, when in benefits from huge code elimination like in this example. Just wanted to avoid premature usage before.
Demo
Visually without a change
Checklist: