Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[✨] Adding a signal dispatcher for component like in vue #183

Closed
astraldev opened this issue Mar 21, 2023 · 5 comments
Closed

[✨] Adding a signal dispatcher for component like in vue #183

astraldev opened this issue Mar 21, 2023 · 5 comments

Comments

@astraldev
Copy link

Is your feature request related to a problem?

I want to create a component that emits a signal whenever a button is clicked and the event should be handled by the parent component but I am using @builder.io/mitosis to build. Other than that, it is practically impossible for a component to emit a signal.

Describe the solution you'd like

Creating a hook for signal emission or just using a this.emit('<SIGNALNAME>') to emit a signal

Describe alternatives you've considered

None

Additional context

If possible, able to accept mitosis integration

@wmertens
Copy link
Member

@astraldev can't you pass a signal via context or props, and then the child component can change the value, which notifies every listener including parents?

@gioboa
Copy link
Member

gioboa commented Oct 14, 2024

@astraldev is it solved?

Copy link

Hello @astraldev. Please provide the missing information requested above.
Issues marked with STATUS-2: missing info will be automatically closed if they have no activity within 14 days.
Thanks 🙏

@astraldev
Copy link
Author

This was a feature request, I am yet to test it.
If there's a need to close the issue, then fine, although a test would be made in like 2 week

@gioboa
Copy link
Member

gioboa commented Oct 17, 2024

I see, thanks @astraldev
I move this issue to qwik-evolution repo to create a RFC discussion for this.
Here is our Qwik RFC process thanks.

@gioboa gioboa transferred this issue from QwikDev/qwik Oct 17, 2024
@github-project-automation github-project-automation bot moved this to In Progress (STAGE 2) in Qwik Evolution Oct 17, 2024
@github-actions github-actions bot added [STAGE-2] incomplete implementation Remove this label when implementation is complete [STAGE-2] not fully covered by tests yet Remove this label when tests are verified to cover the implementation [STAGE-2] unresolved discussions left Remove this label when all critical discussions are resolved on the issue [STAGE-3] docs changes not added yet Remove this label when the necessary documentation for the feature / change is added [STAGE-3] missing 2 reviews for RFC PRs Remove this label when at least 2 core team members reviewed and approved the RFC implementation labels Oct 17, 2024
@gioboa gioboa removed this from Qwik Evolution Oct 17, 2024
@gioboa gioboa removed [STAGE-2] incomplete implementation Remove this label when implementation is complete [STAGE-2] not fully covered by tests yet Remove this label when tests are verified to cover the implementation [STAGE-2] unresolved discussions left Remove this label when all critical discussions are resolved on the issue [STAGE-3] missing 2 reviews for RFC PRs Remove this label when at least 2 core team members reviewed and approved the RFC implementation [STAGE-3] docs changes not added yet Remove this label when the necessary documentation for the feature / change is added labels Oct 17, 2024
@QwikDev QwikDev locked and limited conversation to collaborators Oct 17, 2024
@gioboa gioboa converted this issue into discussion #184 Oct 17, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants