Core Data: Fix field conditions in 'getRevision' selector#71629
Core Data: Fix field conditions in 'getRevision' selector#71629
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Flaky tests detected in 9025b67. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/17669281785
|
ramonjd
left a comment
There was a problem hiding this comment.
Thanks for the follow up @Mamaduka 🙇🏻
Both selectors share 99% of the logic and that unfortunately includes bugs
Do you see any benefit in combining?
If I recall correctly, we kept it separate "just in case" since we didn't want to end up in the inverse situation where they share 99% of logic and we need to split it up to add custom logic 🙃
I think that would be hard to do without breaking changes and increasing the complexity. |
What?
Related #71474.
PR applies recent fixes from the
getEntityRecordselector to thegetRevision. Both selectors share 99% of the logic and that unfortunately includes bugs.Why?
When a component requests a full entity record, it expects to receive
undefinedor the whole record. Returning partial data can lead to unexpected failures as described in the issue.Testing Instructions