Adding some flexibility on `svelte/no-navigation-without-resolve`

[jycouet]

Description

As the author of vite-plugin-kit-routes, I would like to make use of this rule to ease the transfert from vite-plugin-kit-routes to native svelteKit when all features will be there.

Native SvelteKit way

<script lang="ts">
	import { resolve } from '$app/paths';
</script>

<a href={resolve('/about')}>About</a>

vite-plugin-kit-routes way

<script lang="ts">
	import { route } from '$lib/ROUTES';
</script>

<a href={route('/about')}>About</a>

---

What about having in the configuration:

  importKey: 'resolve',
  fromKey: '$app/paths'

It could probably help with localizeHref issues as well (saw it on #1314)

What do you think ?
If you link the idea, I can probably give a try to implement.

[marekdedic]

I'll have to take a look at vite-plugin-kit-routes to say more. But I'd like to add support for detecting resolved routes based on TS types, which I guess could fix this as well.

[jycouet]

My vite-plugin-kit-routes is managing things a bit differently and handles searchParams, anchors (that are not today in native resolve).
That's why I don't really see how to connect to two. The goal will be in the end to fully remove mine in favor of the native way.

Maybe I'm shooting myself in the foot but I would say that it's not a priority ;)

About my proposal, don't you think it can make sense?