You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, when using Client Routing, vite-plugin-ssr automatically intercepts links. You can opt-out with rel="external" (e.g. <a href="/admin" rel="external">).
Instead of opt-out, there could be a new config disableAutomaticLinkInterception, together with a new attribute data-vike-link to opt into Client Routing (e.g. <a href="/product/42" data-vike-link>).
The config can be set in a non-global fashion, i.e. each page can have a different disableAutomaticLinkInterception setting.
// /dashboard/+config.js// The links displayed at URL `/dashboard` *aren't* intercepted exportdefault{disableAutomaticLinkInterception: true}
// /product/@id/+config.js// The links displayed at URL `/product/42` *are* intercepted exportdefault{disableAutomaticLinkInterception: false}
The text was updated successfully, but these errors were encountered:
Implemented. Set window._disableAutomaticLinkInterception = true and use <a data-vike-link>.
⚠️_disableAutomaticLinkInterception will be removed in the next major release. Because, in the next major release, the link interceptor will be able to check whether the URL matches the route of a page, making _disableAutomaticLinkInterception obsolete. (The change requires a breaking change and that's why it can't be released already as v0.4.x.)
Description
By default, when using Client Routing, vite-plugin-ssr automatically intercepts links. You can opt-out with
rel="external"
(e.g.<a href="/admin" rel="external">
).Instead of opt-out, there could be a new config
disableAutomaticLinkInterception
, together with a new attributedata-vike-link
to opt into Client Routing (e.g.<a href="/product/42" data-vike-link>
).The config can be set in a non-global fashion, i.e. each page can have a different
disableAutomaticLinkInterception
setting.The text was updated successfully, but these errors were encountered: