-
Notifications
You must be signed in to change notification settings - Fork 618
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
fix(field-*): Remove unneeded fieldRegistry.unregister
calls
#2454
Conversation
This PR fixes part of #2194. I think you should also fix the other todos so we can close the issue entirely; all are marked with the issue number. |
OK. I did this bit unaware of the cleanup issue because it had come up in the forum as the warnings appear to be causing developer concern. |
Since FieldAngle, FieldColour and FieldMultilineInput are no longer in core, there's no longer any need for their corresponding plugins to unregister the built-in version.
For some reason the last time we ran publish, the publish commit 7d3e23f removed all the trailing newlines from our package-lock.json files. In google#2453 rachel-fenichel proposes adding these files to our .prettierignore.rc, but for now I'll just fix the files so that the format check passes.
087db5b
to
d591183
Compare
d591183
to
615a08e
Compare
OK, the history of this PR is pretty chaotic due to Git-fu (and more particularly GitHub-fu) shortcomings on my part, but the code is now ready for review and now deals with all all remaining instances of |
The basics
The details
Fixes #2194.
Proposed Changes
Remove unneeded
fieldRegistry.unregister
calls fromplugins/field-angle
,field-colour
andfield-multilineinput
's register functions.Also remove the
unregisterBlocks
test helper functions, which are no longer needed for similar reasons.Reason for Changes
Since
FieldAngle
,FieldColour
andFieldMultilineInput
are no longer in core, there's no longer any need for their corresponding plugins to unregister the built-in version.