solid-router

solid-router copied to clipboard

useBeforeLeave event.defaultPrevented not updated

2

### Describe the bug When you use `useBeforeLeave` multiple times, each listener receives a copy of the event, therefore an early listener cannot know if a later listener did call...

katywings

useCurrentMatches only returns one match

1

### Describe the bug When I use useCurrentMatches with the FileRouter and nested paths, I only get one match, i.e. `['test1/test2/test3']` instead of `['test1', 'test2', 'test3']` ### Your Example Website...

RndUsername

This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically....

github-actions[bot]

preserve headers in `query()`'s `handleResponse()`

1

this patch is currently being dogfooded in a real world application ([PetScanner's web app](https://petscanner.com/app)) as it says in the title, I found another place where headers weren't being preserved

samualtnorman

fix(type): allow value from `Params` and `SearchParams` to be optional

1

There is no way for us to know if these params is obligated or optional from the input. So it is safer to assume that they can be undefined.

ngdangtu-vn

Fix #519: Support `in` operator for useParams()

1

Fixes #519

kcirtaptrick

Release 1.0.0

1

The `@solidjs/router` API hasn't changed for about a year (since the SolidStart v1), same as Solid Meta, so it seems reasonable to stabilize the current api surface, and keep following...

birkskyum

Suspense don't work when switching routes

6

### Describe the bug I create routes like this ``` { path: "/", component: (props) => ( {props.children} ), children: [ { path: "", component: Page, }, { path: "test",...

FanetheDivine

### Describe the bug ```js "foo" in useParams() // always evaluates to false "foo" in { ...useParams() } // can evaluate to true or false ``` I assume this has...

samualtnorman

The current design of `"use server"` and combined with `query()` is inherintly type unsafe

5

### Describe the bug The expected usage of `query()` with SolidStart's `"use server"` looks something like this: ```js const getUser = query(async (email: string) => { "use server" // `email`...

samualtnorman