feat: add clear cache button to publish - #494
Merged
Merged
Conversation
Let users force a full cache purge of the published site from the publish popover once the site is live. Guarded by a confirmation dialog explaining it is only useful for large sites and that pages are slower on first visit until cached again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a "Clear cache" button to the publish popover so users can force a full cache purge of their published website. It appears next to the Publish/Update button only once the site has been published, and is guarded by a confirmation dialog that explains when and why it's needed.
Changes
PublishPopover, shown only when the site is already publishedcacheApi.clearAll()helper (POST /ycode/api/cache/clear-all) — no new backend codeTest plan