-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
DateTime: Remove deprecated props (and fix static analysis action in trunk) #50724
Conversation
Size Change: -5.96 kB (0%) Total Size: 1.39 MB
ℹ️ View Unchanged
|
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.
Haven't tested this but the code LGTM 👍
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.
👍 Checked that date dropdown still works in post settings in the post editor
👍 DateTimePicker in Storybook works a treat
Thanks for the reviews! All actions appear to be passing now, so I'll merge this in. |
Was the package-lock change intentional? I'm seeing a diff now when running |
Yes, without it the unit tests action was failing. It's the main thing that changes when updating |
For full visibility, since it's probably a bit unusual combining these two things in the one PR:
Usually I'd prefer to do these in two separate PRs, but figured it'd be better to prioritise unblocking merging to |
What?
Fix failing build(s) on trunk.
Remove deprecated props in the
DateTime
component (__nextRemoveHelpButton
and__nextRemoveResetButton
).Also, bump
caniuse-lite
version, using the same approach as in #46093.Why?
The deprecated props had a version number set to
15.8
for when they were due to be deprecated. This causes the build ontrunk
to fail now that Gutenberg15.8
has been released:Previously, the removal time was bumped six months back in #46006. Now that it's been a year since the props were deprecated, let's go ahead and remove them.
How?
__nextRemoveHelpButton
and__nextRemoveResetButton
props.__nextRemoveHelpButton
or__nextRemoveResetButton
were set tofalse
To fix
caniuse-lite
unit test failures, borrowing from #46093:Ran
npx browserslist@latest --update-db
which updatedpackage-lock.json
with the new version of caniuse-lite. Also updated a few snapshot tests as needed.Testing Instructions
DateTime
component in Storybook and ensure it works correctly. (npm run storybook:dev
)Testing Instructions for Keyboard
Screenshots or screencast