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 the core module is a giant monolith which I build, because I ran into massive import loop issues. Turns out by using the dependency inversion principle this could be avoided and the code could be reorganised again. I would like to implement it for readability alone but I can image this will have some other benefits too.
The text was updated successfully, but these errors were encountered:
Turns out it is not as easy as I thought it would be. Since we have a somewhat bidirectional relation ship between the classes the interface approach kind of falls apart. Need to put more research into this.
Description
Currently the core module is a giant monolith which I build, because I ran into massive import loop issues. Turns out by using the dependency inversion principle this could be avoided and the code could be reorganised again. I would like to implement it for readability alone but I can image this will have some other benefits too.
The text was updated successfully, but these errors were encountered: