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

✨ Add drop cache buttons #899

Merged
merged 2 commits into from May 16, 2023
Merged

✨ Add drop cache buttons #899

merged 2 commits into from May 16, 2023

Conversation

ajnart
Copy link
Owner

@ajnart ajnart commented May 15, 2023

🤖 Generated by Copilot at d713d5f

Summary

🧹🗑️🔘

This pull request adds a new feature to the app's settings that allows the user to clear the cache of different queries. It introduces a new component CacheButtons that handles the UI and logic of the feature, and renders it in the CommonSettings component.

CacheButtons new
Manage queries with mantine
Autumn leaves the old

Walkthrough

  • Add a new component CacheButtons to allow the user to clear the cache of different queries (link)
  • Import and render the CacheButtons component in the CommonSettings component, after the LanguageButtons and before the ThemeButtons (link, link)

@vercel
Copy link

vercel bot commented May 15, 2023

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

Name Status Preview Comments Updated (UTC)
homarr 🛑 Canceled (Inspect) May 15, 2023 8:29am

@ajnart ajnart changed the title Add drop cache buttons ✨ Add drop cache buttons May 15, 2023
@vercel
Copy link

vercel bot commented May 16, 2023

Deployment failed with the following error:

Resource is limited - try again in 3 hours (more than 100, code: "api-deployments-free-per-day").

@ajnart ajnart merged commit be5c60f into dev May 16, 2023
3 of 4 checks passed
@ajnart ajnart deleted the drop-cache branch May 16, 2023 04:55
@github-actions
Copy link

📦 Next.js Bundle Analysis for homarr

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

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 365.9 KB (🟡 +4.7 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!

Four Pages Changed Size

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

Page Size (compressed) First Load
/ 78.6 KB (🟡 +3.26 KB) 444.51 KB
/[slug] 78.61 KB (🟡 +3.26 KB) 444.51 KB
/login 1.15 KB (🟡 +70 B) 367.05 KB
/migrate 8.17 KB (🟡 +465 B) 374.07 KB
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

Next to the size is how much the size has increased or decreased compared with the base branch of this 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.

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.

None yet

1 participant