Use global class names for Core Data entities#25378
Merged
Conversation
Collaborator
Contributor
|
| App Name | WordPress | |
| Configuration | Release-Alpha | |
| Build Number | 31562 | |
| Version | PR #25378 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | 5f5e9e0 | |
| Installation URL | 1nqglkek26o90 |
Contributor
|
| App Name | Jetpack | |
| Configuration | Release-Alpha | |
| Build Number | 31562 | |
| Version | PR #25378 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | 5f5e9e0 | |
| Installation URL | 4dmji4idha0uo |
14cc543 to
5f5e9e0
Compare
|
crazytonyli
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





This is a prerequisite for #25377. For most classes that represent Core Entities, we simply use
@objcclass names to put them into the global namespace, which is a recommended practice. This PR updates the remaining classes, so they all follow the same practice.Potential issues: collisions at runtime; unlikely since most of the code is now in Swift.
Note on migration:
WordPress 158is shipping in 26.8, so I added the change to it.