Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
shhdharmen opened this issue Apr 21, 2024 · 1 comment
Open

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

shhdharmen opened this issue Apr 21, 2024 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@shhdharmen
Copy link
Contributor

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
@shhdharmen shhdharmen added the help wanted Extra attention is needed label Apr 21, 2024
@shhdharmen shhdharmen pinned this issue Apr 21, 2024
@shhdharmen shhdharmen changed the title Feature: Make inputs and outputs signal based [CMDK] Feature: Make inputs and outputs signal based Apr 21, 2024
@jshmllr
Copy link

jshmllr commented Sep 3, 2024

Reading about signals today and this looks great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
Community contributions
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jshmllr @shhdharmen