Ok let me see if I can move things into a toy project in a bit and still repo. Appreciate the quick reply. And to confirm using a task in the deinit is the “right” way before isolated deinit correct?
September 23, 2025 at 9:01 PM
Ok let me see if I can move things into a toy project in a bit and still repo. Appreciate the quick reply. And to confirm using a task in the deinit is the “right” way before isolated deinit correct?
Sometimes use a DI system to share the object which owns the state between layers (not environment). Sometimes pass “action” closures although this feels gross/hacky. Not a fan of preferences for this.
February 13, 2025 at 4:43 AM
Sometimes use a DI system to share the object which owns the state between layers (not environment). Sometimes pass “action” closures although this feels gross/hacky. Not a fan of preferences for this.
Really curious if thered be a way to support quote replies and emoji reactions in DMs. Havent looked at the RN code yet to see but assuming the APIs dont support it. Wondering if it could be done completely client side similar to the iMessage/Android approach
November 22, 2024 at 9:44 PM
Really curious if thered be a way to support quote replies and emoji reactions in DMs. Havent looked at the RN code yet to see but assuming the APIs dont support it. Wondering if it could be done completely client side similar to the iMessage/Android approach
Appreciate posting this breakdown. Wish the UX around these local project overrides was improved. This is an area that still feels better with cocoapods IMO.
November 13, 2024 at 3:51 AM
Appreciate posting this breakdown. Wish the UX around these local project overrides was improved. This is an area that still feels better with cocoapods IMO.
Less a question and more an advice request - but it seems to me actor reentrancy is “easy” to conceptually understand but then miss during practical use cases. Do you have any articles on this or “rule of thumb” type design guidelines to avoid common pitfalls here?
November 12, 2024 at 9:42 PM
Less a question and more an advice request - but it seems to me actor reentrancy is “easy” to conceptually understand but then miss during practical use cases. Do you have any articles on this or “rule of thumb” type design guidelines to avoid common pitfalls here?