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
Currently we are adopting modern concurrency within our application and we are making use of Apollo extensively, However the generated objects are not Sendable which makes it hard to adopt modern concurrency without depending heavily on @unchecked Sendable which is sub-optimal and might lead to crashes eventually if the objects are mutated across different threads
Describe the solution you'd like
Introduce a flag for the auto generation script to get rid of the setters in the generated APIs and conform to Sendable for these models
The text was updated successfully, but these errors were encountered:
Thank you for the feedback! This is already being tracked in #2835! We plan to look into this soon. As we know this is causing problems for users adopting Swift concurrency features.
Use case
Currently we are adopting modern concurrency within our application and we are making use of Apollo extensively, However the generated objects are not
Sendable
which makes it hard to adopt modern concurrency without depending heavily on@unchecked Sendable
which is sub-optimal and might lead to crashes eventually if the objects are mutated across different threadsDescribe the solution you'd like
Introduce a flag for the auto generation script to get rid of the setters in the generated APIs and conform to
Sendable
for these modelsThe text was updated successfully, but these errors were encountered: