Skip to content

Reworked no-navigation-without-resolve to be more general and enable more edge cases#1444

Closed
marekdedic wants to merge 3 commits intosveltejs:mainfrom
marekdedic:no-navigation-without-resolve-query-fragment-suffixes
Closed

Reworked no-navigation-without-resolve to be more general and enable more edge cases#1444
marekdedic wants to merge 3 commits intosveltejs:mainfrom
marekdedic:no-navigation-without-resolve-query-fragment-suffixes

Conversation

@marekdedic
Copy link
Copy Markdown
Contributor

@marekdedic marekdedic commented Dec 14, 2025

Fixes #1327

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Dec 14, 2025

🦋 Changeset detected

Latest commit: 117d4f6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
eslint-plugin-svelte Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Dec 14, 2025

Try the Instant Preview in Online Playground

ESLint Online Playground

Install the Instant Preview to Your Local

npm i https://pkg.pr.new/eslint-plugin-svelte@117d4f6

Published Instant Preview Packages:

View Commit

@marekdedic marekdedic force-pushed the no-navigation-without-resolve-query-fragment-suffixes branch 5 times, most recently from 5cf7529 to d995c55 Compare December 15, 2025 09:45
@marekdedic marekdedic marked this pull request as ready for review December 15, 2025 09:53
@marekdedic
Copy link
Copy Markdown
Contributor Author

Hello, I think this is ready for review now - I still want to add more edge cases (ternary expressions, function calls, array access), but those all need to build upon the structural changes introduced to this rule in this PR, so I'd prefer to merge this first and then add those as separate PRs.

I'd recommend reviewing this PR commit-by-commit, as the last commit is mostly building upon the re-structured rule and shows why such a rewrite is needed...

@marekdedic marekdedic force-pushed the no-navigation-without-resolve-query-fragment-suffixes branch from d995c55 to 838a515 Compare December 16, 2025 15:25
@marekdedic marekdedic force-pushed the no-navigation-without-resolve-query-fragment-suffixes branch from 838a515 to c77c5b5 Compare January 8, 2026 12:52
@marekdedic
Copy link
Copy Markdown
Contributor Author

Rebased and ready for review :)

@ota-meshi
Copy link
Copy Markdown
Member

The changes are so big that I think I'll need a large chunk of time to review this.
Because of this, I'm having trouble getting started on this review.
Could you split this PR into several PRs?
I think that would ultimately result in a faster release.

@marekdedic marekdedic force-pushed the no-navigation-without-resolve-query-fragment-suffixes branch from c77c5b5 to 673a9c6 Compare January 18, 2026 22:57
@marekdedic
Copy link
Copy Markdown
Contributor Author

@ota-meshi Thanks. I'll try to make smaller PRs, however, for some things such as this one, they can only be done sequentially :/

Let's start with #1461.

@marekdedic marekdedic force-pushed the no-navigation-without-resolve-query-fragment-suffixes branch from 673a9c6 to 4ab6bc9 Compare January 23, 2026 10:58
@marekdedic marekdedic force-pushed the no-navigation-without-resolve-query-fragment-suffixes branch from 4ab6bc9 to a0a5255 Compare February 17, 2026 10:30
@marekdedic
Copy link
Copy Markdown
Contributor Author

marekdedic commented Mar 5, 2026

Closing in favor of #1482. Most of the refactoring has already been merged in #1476 anyways.

@marekdedic marekdedic closed this Mar 5, 2026
@marekdedic marekdedic deleted the no-navigation-without-resolve-query-fragment-suffixes branch March 5, 2026 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

no-navigation-without-resolve doesn't work with search params

2 participants