-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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: Add 'Change Event Callback' pattern doc #33216
base: master
Are you sure you want to change the base?
Docs: Add 'Change Event Callback' pattern doc #33216
Conversation
📊 Bundle size report✅ No changes found |
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.
Some brief typos and a question, feel free to disregard if you disagree
🤜🤛
📊 Bundle size report✅ No changes found |
Pull request demo site: URL |
* @param data - A data object with relevant information, | ||
* such as open value and type of interaction that created the event | ||
*/ | ||
// eslint-disable-next-line @nx/workspace-consistent-callback-type -- can't change type of existing callback |
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.
This is a deprecated callback type. What about use an example that uses the new callback type? For example TagPicker onOpenChange
?
Line 43 in d77384f
onOpenChange?: EventHandler<TagPickerOnOpenChangeData>; |
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 see the first example is all taken from dialog. So maybe just add a comment somewhere here pointing to a component that uses the new type like TagPicker
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.
Good catch thank you! I'll replace this with the latest
Implementation of Change Event pattern to document avoiding potential breaking changes and recommended architecture.