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

Mobile menu #469

Merged
merged 32 commits into from
Aug 12, 2024
Merged

Mobile menu #469

merged 32 commits into from
Aug 12, 2024

Conversation

luis-herasme
Copy link
Member

@luis-herasme luis-herasme commented Jul 31, 2024

Checklist

  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

Description

  1. Adds MobileMenu component.
  2. Refactored the menu data out of the menu so that the normal menu and the mobile menu can share the same data.
  3. Fixes a small error inside the button component of the icon variant, causing the icon to have a width of zero

Related Issue

Closes #436

Screenshots:

image

image

Update:

2024-08-01.18-57-20.mp4

Copy link

changeset-bot bot commented Jul 31, 2024

🦋 Changeset detected

Latest commit: 61703fc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@blobscan/web Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Jul 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
blobscan-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 11, 2024 5:45pm
blobscan-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 11, 2024 5:45pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
blobscan-gnosis ⬜️ Ignored (Inspect) Visit Preview Aug 11, 2024 5:45pm
blobscan-holesky ⬜️ Ignored (Inspect) Visit Preview Aug 11, 2024 5:45pm
blobscan-mainnet ⬜️ Ignored (Inspect) Visit Preview Aug 11, 2024 5:45pm
blobscan-sepolia ⬜️ Ignored (Inspect) Visit Preview Aug 11, 2024 5:45pm

Copy link
Contributor

github-actions bot commented Jul 31, 2024

📦 Next.js Bundle Analysis for @blobscan/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 264.41 KB (🟡 +18.79 KB)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Ten Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/ 352.23 KB 616.64 KB 176.18% (🟢 -4.88%)
/address/[address] 26.62 KB 291.03 KB 83.15% (🟢 -4.89%)
/blob/[hash] 25.31 KB 289.73 KB 82.78% (🟢 -4.89%)
/blobs 15.76 KB 280.17 KB 80.05% (🟢 -4.88%)
/block/[id] 11.76 KB 276.17 KB 78.91% (🟢 -4.89%)
/blocks 13.49 KB 277.9 KB 79.40% (🟢 -4.88%)
/stats/blob 336.46 KB 600.87 KB 171.68% (🟢 -4.81%)
/stats/block 337.48 KB 601.89 KB 171.97% (🟢 -4.81%)
/stats/tx 336.58 KB 601 KB 171.71% (🟢 -4.80%)
/txs 20.03 KB 284.44 KB 81.27% (🟢 -4.88%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

Copy link

codecov bot commented Jul 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@f631c7c). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #469   +/-   ##
=======================================
  Coverage        ?   89.83%           
=======================================
  Files           ?      146           
  Lines           ?     9630           
  Branches        ?     1020           
=======================================
  Hits            ?     8651           
  Misses          ?      979           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@PJColombo PJColombo left a comment

Choose a reason for hiding this comment

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

Looking good!

There are some ideas I had in mind for this. I forgot to add the necessary context to this issue :/.

@PJColombo
Copy link
Member

Another issue: the menu is not showing in the top bar for any section other than the homepage.

image

@PJColombo
Copy link
Member

I updated the issue with the design that I had in mind

Copy link
Member

@PJColombo PJColombo left a comment

Choose a reason for hiding this comment

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

Nice job!

It’s starting to take shape nicely.

I feel the current components can get some extra refactoring: rename some of them, abstract the side panel logic, restructure them, etc.

apps/web/src/components/NavMenusSection/MobileMenu.tsx Outdated Show resolved Hide resolved
apps/web/src/components/NavMenusSection/MobileMenu.tsx Outdated Show resolved Hide resolved
apps/web/src/components/Rotable.tsx Show resolved Hide resolved
apps/web/src/components/NavMenusSection/NavItem.tsx Outdated Show resolved Hide resolved
apps/web/src/components/NavMenusSection/data.tsx Outdated Show resolved Hide resolved
apps/web/src/components/NavMenusSection/data.tsx Outdated Show resolved Hide resolved
apps/web/src/components/NavMenusSection/data.tsx Outdated Show resolved Hide resolved
apps/web/src/components/NavMenusSection/data.tsx Outdated Show resolved Hide resolved
apps/web/src/components/NavMenusSection/MobileMenu.tsx Outdated Show resolved Hide resolved
- Improve components names
- Separate `SidebarNavigationMenu` from `NavigationMenus`
- Re-add `Menu` component to `NavigationMenus` to keep consistency with `SidebarNavigationMenu to keep consistency with `SidebarNavigationMenu``
…hen the user is on the corresponding URL route
@PJColombo
Copy link
Member

PJColombo commented Aug 11, 2024

Nice job!

I pushed a few commits fixing some extra things.

Some things I'd like to point out:

  • I made some component renaming changes.
  • I rollbacked the change I requested about separating all NavItem components from the NavigationMenus and I put them back again there to maintain consistency with the SidebarNavigationMenu component, where the navigation components are also kept within the same file.

Copy link
Member

@PJColombo PJColombo left a comment

Choose a reason for hiding this comment

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

LGTM!. Waiting for another approve so we can merge this

apps/web/src/components/NavMenusSection/index.tsx Outdated Show resolved Hide resolved
apps/web/src/components/NavMenus.tsx Outdated Show resolved Hide resolved
Copy link
Member

@PabloCastellano PabloCastellano left a comment

Choose a reason for hiding this comment

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

looks good at preview

transition: "transform 0.6s",
}}
>
<div>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could we use <> fragment instead?

Copy link
Member

Choose a reason for hiding this comment

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

This component is actually outdated

}

return (
<div>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
<div>
<>

I would use fragment instead as we avoid to add an unnecessary div in the DOM tree

Copy link
Member

Choose a reason for hiding this comment

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

This component is actually outdated

@luis-herasme luis-herasme merged commit e8bb0e5 into main Aug 12, 2024
14 checks passed
@github-actions github-actions bot mentioned this pull request Aug 12, 2024
@PJColombo PJColombo deleted the mobile-menu branch August 12, 2024 22:39
@PJColombo PJColombo restored the mobile-menu branch October 29, 2024 11:30
@PJColombo PJColombo deleted the mobile-menu branch October 29, 2024 11:31
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.

Create a sidebar navigation menu for mobile views
4 participants