-
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
Core Data: Remove entity config '__experimentalNoFetch' flag checks #63303
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. |
Size Change: -29 B (0%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
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.
Looking through wpdirectory I think we're fine here but it's always painful to go through the results of plugins that "bundle" packages.
I also searched for wpdirectory and GitHub repos — no usage besides Gutenberg forks. |
…ordPress#63303) Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
…ordPress#63303) Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
What?
PR removes
entityConfig.__experimentalNoFetch
checks from resolvers and selectors.Why?
It was introduced initially to handle a particular case in the now-removed Navigation editor (#34839). I don't see a reason for core entities to use this flag.
Testing Instructions
All CI checks should be green.