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
First, thank you for all the open source work you have been doing at pointfree.co. It's been a great source of inspiration and an amazing learning resource for me the past couple years!
I'm working on a large modularised codebase mostly built in Vanilla SwiftUI. I have several modules that encapsulate some features that are reused in multiple (If not all in some cases) feature modules.
I'm currently importing those modules directly into my feature modules when I need them but that causes an increased build time and transitively import dependencies that are really only implementation details of those reusable feature modules. A similar problem was brought up during the SwiftUI Navigation: Decoupling episode I believe.
I was wondering if you explored any ideas to reduce this coupling? I thought about a similar approach used for dependencies, separating interface and implementation in different modules, but I'm struggling writing a good interface for this.
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
-
Hey there! 👋
First, thank you for all the open source work you have been doing at pointfree.co. It's been a great source of inspiration and an amazing learning resource for me the past couple years!
I'm working on a large modularised codebase mostly built in Vanilla SwiftUI. I have several modules that encapsulate some features that are reused in multiple (If not all in some cases) feature modules.
I'm currently importing those modules directly into my feature modules when I need them but that causes an increased build time and transitively import dependencies that are really only implementation details of those reusable feature modules. A similar problem was brought up during the SwiftUI Navigation: Decoupling episode I believe.
I was wondering if you explored any ideas to reduce this coupling? I thought about a similar approach used for dependencies, separating interface and implementation in different modules, but I'm struggling writing a good interface for this.
Thank you!
Arthur
Beta Was this translation helpful? Give feedback.
All reactions