You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought of this RE background thread operations for SwiftData:
The whole time we were passing models created on a background context to the main thread, so it can cause crashes because the model is tied to its own context (background) while we use it on main. And changes on background aren't synchronized with main.
So after doing the BG operations (syncing with API), we return the ids of the models then perform a load on these ids from main so that these models are tied to main.
Relevant Resources
(Feature Owner, Developer) Attach links to resources such as Figma files, technical documentation, etc.
(Developer) Add child issues (technical or high level) that will help you modularize your implementation this feature.
Task 1 ...
Task 2 ...
When beginning work on a task, click on the ... button to the right of the task and click on Convert to Issue to create a child issue linked to this parent issue.
Implementation Plan (optional)
(Developer) Write an implementation plan here, or attach a link to a document containing it.
The text was updated successfully, but these errors were encountered:
Description
I thought of this RE background thread operations for SwiftData:
Relevant Resources
(Feature Owner, Developer) Attach links to resources such as Figma files, technical documentation, etc.
Child Issues
(Developer) Add child issues (technical or high level) that will help you modularize your implementation this feature.
When beginning work on a task, click on the
...
button to the right of the task and click onConvert to Issue
to create a child issue linked to this parent issue.Implementation Plan (optional)
(Developer) Write an implementation plan here, or attach a link to a document containing it.
The text was updated successfully, but these errors were encountered: