Is anyone planning on supporting signals in router parameters?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 365
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
The @Input decorator is still needed for supporting route parameters. Then new signal inputs don't work. Is this option soon supported?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating how route parameters are connected to Angular @Input decorators and why signal inputs do not work in this path. The issue is complete when route parameters can be supported by signal inputs without requiring @Input; the payload names no files or tests, so the relevant entry points must first be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100