Skip to content

Using signal inputs in computed signals is not supposed #454

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.

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

Closed
003marek opened this issue Jun 13, 2024 · 1 comment · Fixed by #455
Closed

Using signal inputs in computed signals is not supposed #454

003marek opened this issue Jun 13, 2024 · 1 comment · Fixed by #455
Assignees

Comments

@003marek
Copy link

In my use case I have a signal input that I later use in a computed signal. In my test I use render function with componentProperties set. After running the tests I see an error inside computed signal that my signal input is not a function. I believe it is caused by the line delete componentInstance[key] in update function in testing-libarary.ts file.

@003marek 003marek changed the title Using signal inputs in computed signal is not supposed Using signal inputs in computed signals is not supposed Jun 13, 2024
@timdeschryver timdeschryver self-assigned this Jun 13, 2024
@timdeschryver
Copy link
Member

timdeschryver commented Jun 14, 2024

Hello @003marek do you have a reproduction?
As an example see #454.
You might need to use componentInputs instead of componentProperties though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants