Skip to content
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

Fixes cherry-picked to be included in WordPress 5.3.1 #18932

Merged
merged 3 commits into from
Dec 5, 2019

Conversation

youknowriad
Copy link
Contributor

ellatrix and others added 3 commits December 5, 2019 09:45
…rs when the relevant config is not loaded. (#18559)

* Core Data: Add checks to selectors to avoid throwing errors when the relevant config is not loaded.

* Core Data: Throw when `editEntityRecord` targets an entity without a config.

* Core Data: Fix default value typo in `getEntityRecordNonTransientEdits`.

* Core Data: Test the behavior of `editEntityRecord` and `getEntityRecordNonTransientEdits` on entities without configs.
* Remove CollegeHumor from embed provider since the service doesn’t exists anymore.

* Update deprecation logic

* Update deprecated pattterns

* Remove unwanted patterns

* lint fixes

* undo unwanted changes in package-lock.json

* remove unwanted changes, second pass

* Remove CollegeHumor from embed provider since the service doesn’t exists anymore.

* Update deprecation logic

* Update deprecated pattterns

* Remove unwanted patterns

* lint fixes

* undo unwanted changes in package-lock.json

* remove unwanted changes, second pass
Copy link
Member

@gziolo gziolo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, let's publish and test with WordPress core 👍

@ZebulanStanphill
Copy link
Member

ZebulanStanphill commented Dec 5, 2019

Is it too late to get #18842 cherry-picked into WP 5.3.1?

@youknowriad
Copy link
Contributor Author

@ZebulanStanphill It is, unfortunately, I mean it's not strict entirely we can still add things but it's not a simple process so I'm thinking #18842 is not critical enough to perform this again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants