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
[Vue] migrate date-picker and other period-selector related components #18213
Conversation
…ty method (all untested)
…se v-model, add event parameters to createAngularAdapter, allow translate to use variadic args or one string array + rebuild
…s in between nodes while vue 3 does not
…ndling to just reset back to the previous date since it was easier in vue to do that)
@sgiehl looks like tests are passing, this one should be ready to review. |
Actually, there's still one issue here, I'd wait a bit. |
@sgiehl this is ready for review now. |
that looks good to me. |
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.
Left a minor comment. Besides that the code looks fine and the tests seems still to pass. Feel free to merge @diosmosis
|
||
if (!(date instanceof Date)) { | ||
try { | ||
date = $.datepicker.parseDate('yy-mm-dd', date); |
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.
any reason for not using Periods/utilities/parseDate
? I know it's handling some stuff more than needed, but might be good to minimize the direct usage of the datepicker methods, so it's easier to switch it at some point maybe.
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.
No reason, I missed this. You're right it should use the typescript method.
Description:
This PR is based off of #18193.
Changes:
Notes:
setup()
) vs. the options API (properties indefineComponent(...)
) moreso here since it's easier when watching multiple properties at the same time (though it's still hard to do w/ Vue). Neither API is preferred over the other by the vue apparently.Review