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
After moving book back into the network package, testing has become harder because it is now a hard dependency. It would be good to abstract all events that can happen in a handler as its own interface, and inject two interfaces into the handler on start.
Each handler at that point has: log, waitgroup, config, dependencies, events. I would love it if we could abstract the first three into dependencies, but that would be a bit too convoluted of an interface I believe. Go is just not made for this kind of functional programming.
The text was updated successfully, but these errors were encountered:
After moving book back into the network package, testing has become harder because it is now a hard dependency. It would be good to abstract all events that can happen in a handler as its own interface, and inject two interfaces into the handler on start.
Each handler at that point has: log, waitgroup, config, dependencies, events. I would love it if we could abstract the first three into dependencies, but that would be a bit too convoluted of an interface I believe. Go is just not made for this kind of functional programming.
The text was updated successfully, but these errors were encountered: