hello! I am doing some programming with scala on android and I thought about using macwire. Everything works nicely but I got stuck with injecting class which depends on the other one extending module. Example:
class ChatPresenter(chatContractView: ChatContractView) extends ChatContractPresenter { }
trait ChatModule {
import com.softwaremill.macwire._
lazy val presenter: ChatContractPresenter = wire[ChatPresenter]
}
class ChatFragment extends BaseFragment with ChatModule { pesenter. ..... }So I want to use ChatPresenter in ChatFragment. How can I achieve this ?
ok, I resolved my problem, in case someone will have the same problem, I'm leaving solution here:
trait ChatModule {
import com.softwaremill.macwire._
def presenter(chatContractView: ChatContractView) : ChatContractPresenter = wire[ChatPresenter]
}
class ChatFragment extends BaseFragment
with ChatContractView
with ChatModule {
val chatPresenter = presenter(this)
}
Maybe a strange question, but as Macwire is at compile time, is it possible to DI types?
In the mean time I got it to blow up completely: exception during macro expansion:
[error] scala.reflect.macros.TypecheckException: not found: value actionBasedSQLInterpolation
[error] scala.reflect.macros.TypecheckException: not found: value actionBasedSQLInterpolation
Tried @Module
I'm struggeling with this one:
DatabaseSetupAndTeardown.scala:30: Cannot find a public constructor nor a companion object for ...DatabaseProfile
at
lazy val dbProfile = wire[DatabaseProfile]
Which is declared here:
@Module
trait TestModule extends BackendCoreModule {
override lazy val dbProfile = H2TestProfile
}
But DatabaseSetupAndTeardown is a trait and can't be a class
it's mostly a convenience tool so that you don't have to write the constructor call yourself
I'm probably misunderstanding macwire in a very simple way, but if i have a collection of "interfaces" represented as traits, and want to "wire" the implementation of those traits in (think like guice here I guess?), how would that work with macwire? If I'm understanding the example in the README correctly it seems to be wiring only the implementations themselves.
in tests you can make TestModule which will extend MainModule and override that wire with some MockDatabaseDao
Howdy.. is there a way to make circular dependencies work with macwire? I'm on macwire 1.0.x, Scala 2.11, Play 2.3.x although I could upgrade to macwire 2.x if necessary. In my case, I have service A depend on service B & service B depend on service A, so I would expect other people have hit this situation. Assume that in my case it's a large codebase and I can't quite refactor to remove those cases
will appreciate suggestions on better approaches, if there are any
@joprice macwire or not, I would say that getting more type-safety is usually beneficial, esp when there are many primitives around :) All three options you mention have different use-cases, e.g. type-tagging has the benefit that you can use any existing type as a tag so I've used that to tag the
Long id of an entity with the type of the entity. Otherwise I'd say some kinds of wrapper objects
I have the test class extended from the module trait
I guess it is impossible to override it for just one test then as the wiring happens at compile time
which kind of makes sense, as you want a different dependency for each test in your scenario
function is not special in any way :)