dispatch
allows for optional details, but the corresponding events doesn't account for that
#10680
Unanswered
kenteramin
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there!
I've noticed that
dispatch
that we get by typingcreateEventDispatcher<{ something: string }>
will allow to dispatch the event withundefined
whereas on the handleron:something={event => {}}
the event type won't be optionalevent: CustomEvent<string>
.Is it intentional? Can I do something about it? It creates quite some grief for me :))
Beta Was this translation helpful? Give feedback.
All reactions