Last 12 weeks · 0 commits
Describe the bug solid-router uses the wrong way to encode path parameters. It uses (which is for query strings) instead of . This causes to be encoded as . https://github.com/solidjs/solid-router/blob/e54fc4a3bc51d0727df052603a7c92d9da8e099b/src/routing.ts#L295C63-L295C81 Your Example Website or App have none Steps to Reproduce the Bug or Issue 1. register a URL with as segment 2. encounter a 404 when navigating to it as it encodes it to . Expected behavior It should navigate to instead. Screenshots or Videos _No response_ Platform OS: macOS Browser: any browser Additional context _No response_
Describe the bug I'm not sure if that's a bug or if I'm doing something wrong, but when I'm trying to use with components loaded via , trying to render it with it returns an empty string. Your Example Website or App https://github.com/kaathewisegit/solid-ssr-issue Steps to Reproduce the Bug or Issue 1. 2. Run or 3. run . It will return an empty string Expected behavior I expected it to return . Replacing with an explicit import and `` makes it work correctly. Platform OS: Alpine Linux 3.24.0_alpha20260127 Browser: none, runtime Node.js v24.13.0
Each of these workflows runs without a top-level block, so its inherits the repository (or org) default, which is frequently read/write for all scopes. Setting explicitly on , keeps the workflow token scoped to what the job actually uses. If a third-party action or transitive dependency in the run were ever compromised, a read-only token limits the damage (no pushes, no releases, no token-backed writes). The change is mechanical and does not alter any step.
Repository: solidjs/solid-router. Description: A universal router for Solid inspired by Ember and React Router Stars: 1314, Forks: 175. Primary language: TypeScript. License: MIT. Open PRs: 10, open issues: 54. Last activity: 2mo ago. Top contributors: ryansolid, rturnq, Brendonovich, birkskyum, atilafassina, Brendan-csel, oedotme, Jutanium, jpdutoit, jchatard and others.