Qwik Router next steps

[wmertens]

dumping my todo list

separate prs:

• add strictLoaders: false to qwik v2 migration
• actions json result should be like loaders, and redirects+errors should be caught
• make rpc$ and deprecate server$. Requires validation, no capture, and single param, includes manifest hash
  • make formAction and deprecate *Action:
    • .submitted is basically just !!value
    • formData can be a separate store
    • move .value.failed to .error.
    • The rest seems unimportant.
    • invalidate all loaders in the current route, unless invalidatesis specified
  • make action calls be server calls with extra param; amend server$recognition
• make pageConfig async

problems:

• extra data serialized, see ssg tests

[Pancio-code]

+1 for "invalidate all loaders in the current route, unless invalidate is specified". Here is a concrete case from a production app on 2.0.0-rc.3 with strictLoaders (the default), in case it helps to shape it.

Case: a multi-tenant app where the session's current company can change. Three actions do it: switching company, deleting it, and leaving it. After any of them almost every loader of the page is stale: the root and group layout loaders (company name, plan limits, notifications bell), the page's own loaders, and loaders of other routes that the client has cached.

Today: an action can only list loaders in invalidate: [...], and with strictLoaders the default is invalidate: []. The action lives in a shared component and cannot know every loader of every route it can be used from, so we post these forms with reloadDocument. The server redirects with Clear-Site-Data and the page reloads fully. That works, but we lose the SPA navigation, and with reloadDocument isRunning never turns true, so we need a sync$ guard against double submits.

What would let us drop that: an "all" form, for example invalidate: "all" or invalidate: true, that re-runs every loader of the current route (layouts included) and also drops the client cache of other routes' loaders. The cache part matters for us: for this kind of action, stale data from another tenant must never come back from the cache on a later navigation.

[maiieul]

As discussed, we need to keep .value.failed as deprecated and make throw new Error go into .error for loaders and async computeds