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

Extract Core Data to ShareExtensionCore #24275

Merged
merged 2 commits into from
Mar 20, 2025

Conversation

kean
Copy link
Contributor

@kean kean commented Mar 20, 2025

This PR extract the Core Data entities, related code, and models to the ShareExtensionCore module. These files used to be duplicated between the app extensions and the app.

To test:

  • Share an image using the share extension
  • Verify that it created a post (as long as it doesn't crash, it should be fine).

I tested that it loads in the app too:

// in app delegate; loads model correctly
let stack = SharedCoreDataStack()
print(stack.managedContext)

Regression Notes

  1. Potential unintended areas of impact

  2. What I did to test those areas of impact (or what existing automated tests I relied on)

  3. What automated tests I added (or what prevented me from doing so)

PR submission checklist:

  • I have completed the Regression Notes.
  • I have considered adding unit tests for my changes.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing checklist:

  • WordPress.com sites and self-hosted Jetpack sites.
  • Portrait and landscape orientations.
  • Light and dark modes.
  • Fonts: Larger, smaller and bold text.
  • High contrast.
  • VoiceOver.
  • Languages with large words or with letters/accents not frequently used in English.
  • Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
  • iPhone and iPad.
  • Multi-tasking: Split view and Slide over. (iPad)

@kean kean added the General label Mar 20, 2025
@kean kean added this to the 25.9 milestone Mar 20, 2025
@dangermattic
Copy link
Collaborator

2 Warnings
⚠️ Modules/Package.swift was changed without updating its corresponding Package.resolved. Please resolve the Swift packages as appropriate to your project setup (e.g. in Xcode or by running swift package resolve).
⚠️ This PR is assigned to the milestone 25.9. The due date for this milestone has already passed.
Please assign it to a milestone with a later deadline or check whether the release for this milestone has already been finished.

Generated by 🚫 Danger

@wpmobilebot
Copy link
Contributor

WordPress Alpha📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
App NameWordPress Alpha WordPress Alpha
ConfigurationRelease-Alpha
Build Numberpr24275-e8894a1
Version25.8
Bundle IDorg.wordpress.alpha
Commite8894a1
App Center BuildWPiOS - One-Offs #11763
Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

@wpmobilebot
Copy link
Contributor

Jetpack Alpha📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
App NameJetpack Alpha Jetpack Alpha
ConfigurationRelease-Alpha
Build Numberpr24275-e8894a1
Version25.8
Bundle IDcom.jetpack.alpha
Commite8894a1
App Center Buildjetpack-installable-builds #10789
Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

@kean kean requested review from mokagio and crazytonyli March 20, 2025 16:44
@kean kean added this pull request to the merge queue Mar 20, 2025
Merged via the queue into trunk with commit 82f1682 Mar 20, 2025
27 checks passed
@kean kean deleted the task/extract-core-data-share-extension branch March 20, 2025 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants