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

feat(web): Create category filter #637

Merged
merged 32 commits into from
Dec 3, 2024
Merged

feat(web): Create category filter #637

merged 32 commits into from
Dec 3, 2024

Conversation

xFJA
Copy link
Collaborator

@xFJA xFJA commented Nov 21, 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

IT BUILDS ON TOP OF #623

A new filter has been added: Category:

  • If 'Others' is selected, the Rollup dropdown filter is disabled
  • If 'Others' is selected and there is a rollup already selected, the dropdown loses its state
  • Removed inweb the none option in the Rollup filter as we can achieve that with the current filter

Related Issue

Closes #594

Screenshots

Screen.Recording.2024-11-21.at.11.37.55.mov

Copy link

changeset-bot bot commented Nov 21, 2024

🦋 Changeset detected

Latest commit: 55b013a

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

This PR includes changesets to release 3 packages
Name Type
@blobscan/api Minor
@blobscan/web Minor
@blobscan/rest-api-server Patch

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 Nov 21, 2024

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

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

Copy link
Contributor

github-actions bot commented Nov 21, 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 332.39 KB (🔴 +86.77 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!

New Pages Added

The following pages were added to the bundle from the code in this PR:

Page Size (compressed) First Load % of Budget (350 KB)
/block_neighbor 251 B 332.63 KB 95.04%
/stats 348.07 KB 680.46 KB 194.42%

Eight 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)
/ 354.57 KB 686.96 KB 196.27% (🟢 -4.22%)
/address/[address] 29.89 KB 362.28 KB 103.51% (🟢 -3.96%)
/blob/[hash] 29.67 KB 362.06 KB 103.45% (🟢 -3.65%)
/blobs 80.74 KB 413.13 KB 118.04% (🟡 +13.69%)
/block/[id] 15.06 KB 347.45 KB 99.27% (🟢 -3.95%)
/blocks 78.48 KB 410.87 KB 117.39% (🟡 +13.69%)
/tx/[hash] 17.54 KB 349.93 KB 99.98% (🟡 +1.22%)
/txs 77.9 KB 410.29 KB 117.23% (🟡 +11.65%)
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.

Category filter allows to filter all the items that doesn't have a rollup related
@xFJA xFJA marked this pull request as ready for review November 21, 2024 05:24
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.

Good job!

What do you think about the following UX suggestions?

  • Can you set 'Rollup' as the default in the Category selector?
  • Can you move 'Rollup' above 'Other' in the list?"

@PJColombo
Copy link
Member

Good job!

What do you think about the following UX suggestions?

  • Can you set 'Rollup' as the default in the Category selector?
  • Can you move 'Rollup' above 'Other' in the list?"

I agree with setting ‘Rollup’ as the default, but I’d prefer to keep the sorting alphabetical.

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.

When selecting multiple rollups on smaller screens, the rollup filter overflows:

Screen.Recording.2024-11-29.at.07.09.58.mov

Also, when navigating to a route with the category query param set the category filter doesnt get set as well

packages/api/src/utils/schemas.ts Outdated Show resolved Hide resolved
@@ -214,6 +221,11 @@ export const withFilters = t.middleware(({ next, input = {} }) => {
filters.transactionCategory = "ROLLUP";
}

filters.transactionCategory =
Copy link
Member

Choose a reason for hiding this comment

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

Is there any particular reason we allow null for category values? I’d prefer restricting it to just the enum values.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

No! Done 👍

apps/web/src/components/Filters/index.tsx Outdated Show resolved Hide resolved
apps/web/src/components/Filters/index.tsx Outdated Show resolved Hide resolved
apps/web/src/components/Filters/RollupFilter.tsx Outdated Show resolved Hide resolved
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.

Found another bug:

The rollup filter is available when the category filter is empty.

image

@PJColombo
Copy link
Member

Additionally, when I first navigate to any of the table pages, the category filter is set, but the route does not contain the corresponding query parameter.

image

@xFJA
Copy link
Collaborator Author

xFJA commented Nov 29, 2024

Finall

  • Set Rollup as the default value
  • Moved Others to the bottom
  • Fixed category init value load from query param

edit:

  • Fixed responsiveness in filters in small devices

cc: @PabloCastellano @PJColombo

Finally, we have agreed to avoid set a default value for the category as we should expect the filters totally empty in a first load. Also, the rollup filter has been disabled when there is no value defined 👍

cc: @PabloCastellano @PJColombo

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.

Added a couple of commits fixing a small style issue and adding a refactoring change

@xFJA xFJA changed the base branch from add-category-column to main December 2, 2024 12:15
Copy link

codecov bot commented Dec 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.72%. Comparing base (025484b) to head (55b013a).
Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #637      +/-   ##
==========================================
- Coverage   88.77%   88.72%   -0.05%     
==========================================
  Files         159      158       -1     
  Lines       10865    10872       +7     
  Branches     1203     1201       -2     
==========================================
+ Hits         9645     9646       +1     
- Misses       1220     1226       +6     

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

@xFJA xFJA force-pushed the create-category-filter branch from 238b9a2 to 9e6b037 Compare December 2, 2024 13:42
@xFJA xFJA merged commit ca30a0f into main Dec 3, 2024
13 of 14 checks passed
@github-actions github-actions bot mentioned this pull request Dec 3, 2024
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 category filter
3 participants