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

zksharding fix #149

Merged
merged 14 commits into from
Dec 18, 2023
Merged

zksharding fix #149

merged 14 commits into from
Dec 18, 2023

Conversation

CallMeOneka
Copy link

No description provided.

@ukorvl
Copy link
Member

ukorvl commented Dec 15, 2023

I didn't check styles, only logic. Because this is the work for the qa engineer, not developer

@@ -0,0 +1,12 @@
@use '~styles/mixins' as *;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the almost similar with LeftColumn. Why not to just create Column component with left/right props? It would be easy to refactor in the future than when you have more components.

@@ -23,37 +24,18 @@

@include mobile {
padding-left: size($spacing12);
padding-top: size($spacing24 - 8);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$spacing16?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Снимок экрана 2023-12-15 в 16 00 43

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, i mean that $spacing24 - 8 is equal to 24 - 8, isn't it right?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is equal to 24 - 8

Judging by the design, the padding should be 24 pixels, but due to the difference in font drawing (Figma and browser), we reduce the paddings to leave dependence on the $spacing24 variable

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this issue relate to the particular font (in our case Helvetica Neue LT Pro) or it is something with drawing font in general? May i ask you to elaborate on this a bit more?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in general, Figma draws the font a little differently, but in this case it is related to a certain font. Throughout the project, I adjusted the margins to the font so that it was pixel perfect

@@ -9,6 +9,7 @@
display: flex;
align-items: flex-start;
padding-bottom: size(91);
margin-top: size(-1);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks hacky, but if there is no other workarounds, okay. Not very important.

@@ -20,6 +20,23 @@ type SecureProps = {
const Secure = ({ className, data: { title, description, content, footer } }: SecureProps) => {
const { isMobile } = useViewport()

const columnContent = useMemo(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page has no reasons to update during runtime in the browser, so useMemo makes no sense.

site/global.d.ts Outdated
@@ -0,0 +1,5 @@
declare global {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like overhead. Consider to just add a type in the component module, like

type Content = {
  title: string
  description: string
  icon: string
}
...
content.reduce<[Array<Content>, Array<Content>]>

@ukorvl ukorvl merged commit 67c74f9 into NilFoundation:master Dec 18, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants