Migrate to Signal-based Input/Output/Queries

Open
#193 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
angular, typescript
Domain
frontend

Research direction

Start by reviewing the repository's component inputs, outputs, and queries alongside the three linked ngxtension migration guides. Inventory the affected components before running the signal-inputs, new-outputs, and queries migrations. Done means the relevant component APIs use signals and existing view behavior remains intact.

Written by the indexing model from the issue text.

Description

angular-client
Desired Changes

The new signal-based input/output/query API enables full reactivity in components, and also assists the migration to OnPush change detection, since signal changes will always trigger view updates.

This migration can be automated by ngxtension's migration schematics:

This migration would involves a great amount of changes and would likely be time-consuming.

Screenshots (as needed)

No response

Dominant language
TypeScript
Stars
5
Forks
1
Avg merge
4d 22h
Merged PRs (30d)
26

Contributor guide

No contributing guide indexed for this repository

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 Northeastern-Electric-Racing/Argos

All issues in Northeastern-Electric-Racing/Argos

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.