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 currently propagate my overridden registered dependencies when I present my TCA feature from a legacy UIKit view controller using a withDependencies(from: self)
With that change that caused my overridden dependencies to not make it down to FeatureA anymore. The way I was able to get things working again was to use the .dependency function to override FeatureA dependencies when I created the reducer like so:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I currently propagate my overridden registered dependencies when I present my TCA feature from a legacy UIKit view controller using a
withDependencies(from: self)
This works great, however recently I decided to make
FeatureA
a child, and introduce a new parent, replacing the code above with:With that change that caused my overridden dependencies to not make it down to
FeatureA
anymore. The way I was able to get things working again was to use the.dependency
function to overrideFeatureA
dependencies when I created the reducer like so:Is this the proper way to ensure the overridden dependencies get propagated down or is there a better way?
Beta Was this translation helpful? Give feedback.
All reactions