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
Copy file name to clipboardExpand all lines: docs/components/link.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,12 @@ interface LinkProps
26
26
}
27
27
28
28
typeTo=string|Partial<Path>;
29
+
30
+
interfacePath {
31
+
pathname:string;
32
+
search:string;
33
+
hash:string;
34
+
}
29
35
```
30
36
31
37
</details>
@@ -136,6 +142,10 @@ You can access this state value while on the "new-path" route:
136
142
let { state } =useLocation();
137
143
```
138
144
145
+
## `reloadDocument`
146
+
147
+
The `reloadDocument` property can be used to skip client side routing and let the browser handle the transition normally (as if it were an `<a href>`).
Copy file name to clipboardExpand all lines: docs/components/nav-link.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,4 +120,8 @@ Adding the `caseSensitive` prop changes the matching logic to make it case sensi
120
120
121
121
When a `NavLink` is active it will automatically apply `<a aria-current="page">` to the underlying anchor tag. See [aria-current][aria-current] on MDN.
122
122
123
+
## `reloadDocument`
124
+
125
+
The `reloadDocument` property can be used to skip client side routing and let the browser handle the transition normally (as if it were an `<a href>`).
0 commit comments