Skip to content

[CMDK] Feature: Make inputs and outputs signal based #3

Description

@shhdharmen

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

Inputs and Outputs are not signal based

Expected behavior

Make inputs and outputs signal based

What is the motivation / use case for changing the behavior?

https://angular.io/guide/signal-inputs#why-should-we-use-signal-inputs-and-not-input

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions