-
Notifications
You must be signed in to change notification settings - Fork 734
Feat/incubator dialog more props and fixes #2251
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
Feat/incubator dialog more props and fixes #2251
Conversation
@M-i-k-e-l |
I understand, but each commit is a change which can be viewed individually and while they are not exactly coupled, in order to have higher confidence in the changes, I wanted to perform a few migrations (while doing other migrations later on). |
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 overall, I wrote some comments :)
if (onModalDismissed) { | ||
LogService.deprecationWarn({component: 'ActionSheet', oldProp: 'onModalDismissed', newProp: 'onDismiss'}); | ||
} |
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.
Today users maybe use both props for two different purposes, are we omitting the onModalDismissed
prop?
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.
onModalDismissed
comes from the ActionSheet
, it is no longer needed with the new Dialog
.
We cannot omit it because that will cause a TS error, I'll add deprecated
to it.
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 understand, but if a user uses our ActionSheet
and passes those both props, with a different callback for each (for some reason) he won't be able to do so anymore.
I agree it's a bit rare and not something that we should care about much, but at least mention somewhere that it's a breaking change.. don't you think?
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.
But the user does not have to send the migrateDialog
prop, this will only be "mandatory" in v7, where we can break the user. If they choose to migrate, they can fix the logic they have.
Not sure if this is clear, but this is not our private ActionSheet
.
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.
Approved, please see my last comment before you merge :)
Description
You can look at individual commits for simplicity.
Incubator.Dialog - add support for a few things (custom elements,
onPress
on the header +width
andheight
in the dialog) and a couple of fixes.Add API for DialogHeader.
Start migration in
ActionSheet
and a couple of screens (and support it onIncubator.WheelPicker
.Naming: I am not sure about a couple of styles names (see TODO), suggestions are welcome.
WOAUILIB-2317
WOAUILIB-3072
Changelog
Incubator.Dialog - add support for a few things, a couple of fixes and start a migration for ActionSheet.