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

[🐞] V2 - “useTask$” only listens for the first change in the client. #7134

Open
devcaeg opened this issue Dec 6, 2024 · 4 comments · May be fixed by #7217
Open

[🐞] V2 - “useTask$” only listens for the first change in the client. #7134

devcaeg opened this issue Dec 6, 2024 · 4 comments · May be fixed by #7217
Labels
COMP: runtime TYPE: bug Something isn't working VERSION: upcoming major

Comments

@devcaeg
Copy link

devcaeg commented Dec 6, 2024

Which component is affected?

Qwik Runtime

Describe the bug

Using a “track” in a “useTask$” causes the client to hear only the first change in the “track” but not the other changes.

Reproduction

https://stackblitz.com/edit/github-6f6maw-u2pxmf?file=src%2Froutes%2Findex.tsx

Steps to reproduce

Make multiples clicks on the “Toggle errors” button, and you will see how only the first error is executed, and you will not hear anymore the change of errors.

System Info

npmPackages:
    @qwik.dev/core: 2.0.0-alpha.1
    @qwik.dev/router: 2.0.0-alpha.1
    typescript: 5.7.2
    undici: 7.0.0 
    vite: 6.0.1

Additional Information

No response
@devcaeg devcaeg added STATUS-1: needs triage New issue which needs to be triaged TYPE: bug Something isn't working labels Dec 6, 2024
@Varixo Varixo added VERSION: upcoming major COMP: runtime and removed STATUS-1: needs triage New issue which needs to be triaged labels Dec 6, 2024
@Varixo Varixo moved this from Backlog to Upcoming in Qwik Development Dec 6, 2024
@JerryWu1234
Copy link
Contributor

@Varixo are you fixing right now? May I pick this version 2 bug?

@JerryWu1234
Copy link
Contributor

JerryWu1234 commented Dec 14, 2024 •
edited
Loading

one Workaround is like this

return {store, from};

@devcaeg
but i'm still working this bug,

@devcaeg
Copy link
Author

devcaeg commented Dec 14, 2024

Yes, that's the way it works. But anyway plugins like modular-forms uses { store, [ Form, ... ] }

@gioboa gioboa mentioned this issue Dec 22, 2024
Open
5 tasks
@Varixo
Copy link
Member

Varixo commented Dec 29, 2024

https://qwikdev-build-v2.qwik-8nx.pages.dev/playground/#f=7VaxDoIwEN39ituAxJAwGCMRnJhNkI2wqauJsjX3717vChxpRR3cZGra8ui9Pu49JZpttgmJZj1aLo%2B4rb2PJ1K2%2BHCh0PaG2tPtnrs8gKVlIOYoMXIDky3HxpksqlWQOadLfjdlVCpJ1rXz%2B%2BtWqzzQ2yI5q0ggSmTD7Jb0PTleGRBXFu%2BT30e%2B2EPLkagjYtqB21h4IXkaxKTjAy6zoDlgPKnxkfZkdKEKQ5uEjKXAKGlvCjlGl2MfD5bK8ucOQO58uZJJnCGHqKrrYw1NdWpIM4KDWLJzjAFzOIFcDIMVxkPGQeM6vL7uRtlO5e1vutFM6P9e9Ite9AQ

@Varixo Varixo linked a pull request Jan 2, 2025 that will close this issue
fix: convert destructured array's props to signal #7217
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
COMP: runtime TYPE: bug Something isn't working VERSION: upcoming major
Projects
Qwik Development
Status: Upcoming
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: convert destructured array's props to signal QwikDev/qwik
3 participants
@JerryWu1234 @Varixo @devcaeg