Skip to content

Commit e3001b3

Browse files
committed
chore: pnpm run update
1 parent 6e26629 commit e3001b3

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

docs/rules/no-navigation-without-resolve.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ description: 'disallow using navigation (links, goto, pushState, replaceState) w
99

1010
> disallow using navigation (links, goto, pushState, replaceState) without a resolve()
1111
12+
- :exclamation: <badge text="This rule has not been released yet." vertical="middle" type="error"> **_This rule has not been released yet._** </badge>
13+
1214
## :book: Rule Details
1315

1416
This rule reports navigation using HTML `<a>` tags, SvelteKit's `goto()`, `pushState()` and `replaceState()` functions without resolving a relative URL. All four of these may be used for navigation, with `goto()`, `pushState()` and `replaceState()` being intended solely for iternal navigation (i.e. not leaving the site), while `<a>` tags may be used for both internal and external navigation. When using any way of internal navigation, the URL must be resolved using SvelteKit's `resolve()`, otherwise the site may break. For programmatic navigation to external URLs, using `window.location` is advised.
@@ -80,10 +82,6 @@ This rule checks all 4 navigation options for the presence of the `resolve()` fu
8082
- [`pushState()` documentation](https://svelte.dev/docs/kit/$app-navigation#pushState)
8183
- [`replaceState()` documentation](https://svelte.dev/docs/kit/$app-navigation#replaceState)
8284

83-
## :rocket: Version
84-
85-
This rule was introduced in eslint-plugin-svelte v2.36.0-next.9
86-
8785
## :mag: Implementation
8886

8987
- [Rule source](https://github.com/sveltejs/eslint-plugin-svelte/blob/main/packages/eslint-plugin-svelte/src/rules/no-navigation-without-resolve.ts)

0 commit comments

Comments
 (0)