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
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
This has come up a few times but I just realised we don't have an issue for it (that I can find).
It'd be cool if there were a way to match paths of arbitrary depth. Happily, there's a really nice idiomatic way we can achieve that, by using rest syntax:
src/routes/foo/[...bar]/baz.html
This would match /foo/a/b/c/baz, and params.bar would equal ['a', 'b', 'c'].
The text was updated successfully, but these errors were encountered:
Ah yes, that’s the issue that I was going to file a couple of days ago, before I decided to shelve the project until Svelte 3 is ready for use!
Spread syntax is indeed a nice solution to it.
For a couple of projects I have in mind, I’d call this not just cool, but essential, given arbitrary nesting structures.
If this is still undone when the dust settles for Svelte 3, I’d be willing to implement it. (On the surface it doesn’t look like it should be particularly difficult.)
This has come up a few times but I just realised we don't have an issue for it (that I can find).
It'd be cool if there were a way to match paths of arbitrary depth. Happily, there's a really nice idiomatic way we can achieve that, by using rest syntax:
This would match
/foo/a/b/c/baz
, andparams.bar
would equal['a', 'b', 'c']
.The text was updated successfully, but these errors were encountered: