Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Is anyone planning on supporting signals in router parameters?

Open
#1,024 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
angular, typescript
Domain
frontend

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.

Description

The @Input decorator is still needed for supporting route parameters. Then new signal inputs don't work. Is this option soon supported?

Dominant language
TypeScript
Stars
365
Forks
138
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ui-router/angular

All issues in ui-router/angular

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.