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.
Closes #6354.
Related to #6489, #6274 and #5305 (we can remove the
breaking change
label from the latter two once this is merged).It's very possible that we'd need to add an
options
object toinvalidate(...)
in future. Since overloaded functions are a terrible idea, that'd mean that to accommodate the no-argument case where you want to invalidate everything, we'd have to do this......which is sinful. A better approach, which happens to be clearer and easier to document, is to create a new
invalidateAll
function:Separately, I think it's probably more useful if the predicate form takes a
URL
instead of a string:Unfortunately this second part is the sort of breaking change that's basically impossible to add a runtime error for. If people think a string (i.e.
url.href
) is preferable, then we could keep it as it is.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0