-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Turn on feature flag to the new Core Data context structure #19433
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
Conversation
You can test the changes in Jetpack from this Pull Request by:
|
You can test the changes in WordPress from this Pull Request by:
|
|
@mokagio Do you mind having a look at this PR? I'd like to merge this sooner so that we can get a maximum amount of testing time. Thanks! |
mokagio
left a comment
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.
@crazytonyli sorry for the long wait. I've been meaning to open #19478 for a suggestion, but kept getting side tracked by other things.
Good to go 👍
…actory-test-suggestion Add a conditional `XCTExpectFailure` in `ContextManagerTests`
All the known issues, which is listed below, of the new
ContainerContextFactoryhave been fixed.Notificationattributes cache #19395.Please note, this PR aims at 21.1 release, so that we have time to test the new context objects structure.
Regression Notes
Potential unintended areas of impact
None.
What I did to test those areas of impact (or what existing automated tests I relied on)
I have turned this feature flag on locally for a while, haven't notified any new issue.
What automated tests I added (or what prevented me from doing so)
None.
PR submission checklist:
RELEASE-NOTES.txtif necessary.