-
Notifications
You must be signed in to change notification settings - Fork 104
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
docs: storybook sync up with event arguments #1977
Conversation
6956707
to
36753c7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Just one super minor suggestion, but I don't mind if this is merged without changing
el, | ||
originalEvent, | ||
index, | ||
}; | ||
eventObj = Object.entries(eventObj) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you'd like you can use Object.fromEntries
here instead of reduce
. I think it's a little cleaner but it is personal preference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it. Looks cleaner. Rolled out the change.
Description
Updated storybook documentation to sync up with the component events. Both DOM and component events are being emitted and storybook displays these events in actions tab. During this process for some component events, marko class information is being emitted. We decided to leave that extra information as is. Other-than that, the callback arguments were appropriately corrected in the storybook documentation.
References
Fixes following
#1930
#1892
#1887
#1890
Screenshots
Page/Section notice
Fake menu button
Confirm dialog
Drawer dialog