-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Revert "Compat: Upgrade admin notices to use Notices module at runtime" #12440
Conversation
(Unreverted)
Erroneous conflict resolution
## 1.1.0 (2018-11-20) | ||
|
||
### New Feature | ||
|
||
- The `createNotice` can now optionally accept a WPNotice object as the sole argument. |
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 never actually went through in #11604. See #11604 (comment) .
Should we close this? An alternative has been merged right? |
@youknowriad #12444 was a safer "revert", while not actually being a proper revert. The code still lingers. The changes here would be more an actual revert. The public-facing interface changes are limited to the |
#12243 is closed. It looks like the original issue was resolved. Does it mean that this PR can be closed, too? |
There is still dead code left to be eliminated. I may want to specifically revisit whether to remove the |
Not sure about the status of dead code these days, but the branch is long-stale, so I doubt it's much use in its current form, so will go ahead and close. |
Related: #11604
Closes #12243
This pull request seeks to effectively revert #11604 .
Notably, since this was included in published releases already, it has been done in such a way that it bumps the major versions of the
edit-post
andnotices
modules to reflect the fact that the revert is a breaking change.Two commits from #11604 have been exempt from the revert (i.e. will remain in master):
These were not strictly relevant to the addition of admin notices compatibility. Ideally, they would have been proposed as separate changes. In omitting them, they reduce the number of changes included in this revert.
Testing instructions:
Verify the inverse of the testing instructions outlined in #11604.