-
Notifications
You must be signed in to change notification settings - Fork 358
[Content]: Solid-Router docs, redirect entry #1223
Copy link
Copy link
Labels
good first issueGood for newcomersGood for newcomershelp wantedLooking for assistance on this issueLooking for assistance on this issueplannedFeatures or content that are planned but not yet in progress.Features or content that are planned but not yet in progress.solid-routerRelated to Solid RouterRelated to Solid RoutersolidstartRelated to SolidStartRelated to SolidStart
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomershelp wantedLooking for assistance on this issueLooking for assistance on this issueplannedFeatures or content that are planned but not yet in progress.Features or content that are planned but not yet in progress.solid-routerRelated to Solid RouterRelated to Solid RoutersolidstartRelated to SolidStartRelated to SolidStart
📚 Subject area/topic
Router
📋 Page(s) affected (or suggested, for new content)
https://docs.solidjs.com/solid-router/reference/response-helpers/redirect
📋 Description of content that is out-of-date or incorrect
The Solid-Router entry for
redirectdoes not have an example for revalidating queries upon redirecting.This obscures a best practice when creating Auth in apps, for example. Because it's recommended to invalidate session-related queries upon logging out and logout usually triggers a redirect - it's a good pattern to have a handy example in our docs.
I noticed that when reviewing a PR for an auth example in SolidStart.
🖥️ Reproduction in StackBlitz (if reporting incorrect content or code samples)
No response