the
registerForClosing would add the instance to a list and return it unmodified
I have usecase question for the wire macro. Most of my Compontents take configuration options (eg. Database name) and other components (eg. Excution context) as a parameter. Now I'd like to use wire in order to provide the components but not the configuration options. Is that even possible?
My rational is that most of the config options are Strings so that would require to tag them all ... which would result in basically writing down a copy of the config file it self mapping all the paths in the config like "system1.database.name" to tags like "System1DatabaseName"
Or is there maybe an other way to avoid this? (Maybe a integration with typesafe config to automatically tag values?)
- how would you determine which parameters should be provided automatically, and which should be provided by hand?
- how would you provide the parameters which a have to provided manually? preferrably in an IDE-friendly way?
This message was deleted
integration with typesafe-config would be possible for sure ... maybe something like this:
- there should be a single dependency of type
Configavailable - any parameters marked with with a config path (*) would be looked up in the config
now there's the question on how you would mark those parameters - with an annotation? but then, what about e.g. default values? any ideas? :)
I'm a little surprised by the following behavior
given a type PlatformsPage with dependencies
class PlatformsPage(platformStore:PlatformStore,platformBackend:(BackendScope[Props,State] => Backend))I'm trying to create a factory method (platformsBackend) as a def.
trait PlatformsModule {
lazy val platformsPage = wire[PlatformsPage]
lazy val platformsStore = wire[PlatformStore]
def platformsBackend(scope:BackendScope[Props,State]):Backend = new Backend(scope)
}This results in an error:
Cannot find a value of type: [japgolly.scalajs.react.BackendScope[spatutorial.client.modules.platform.Props,spatutorial.client.modules.platform.State] => spatutorial.client.modules.platform.Backend]however these versions work
lazy val platformsBackend:BackendScope[Props,State] => Backend = new Backend(_)type BackendFactory = BackendScope[Props,State] => Backend
lazy val platformsBackend:BackendFactory = new Backend(_)can function defs not be used to create factory dependencies?
Sorry if that's clearly stated, or I'm missing something obvious. Macwire has been a joy to use
Have anyone used Macwire 2.0 with Play 2.4? I tried to update but it fails with the following errors:
[error] /home/guersam/workspace/github/macwire/examples/play24/app/com/softwaremill/play24/AppApplicationLoader.scala:36: Found multiple values of type [slick.driver.H2Driver.api.Database]: [List(db, db)]
[error] val seed = wire[Seed]
[error] ^
[error] /home/guersam/workspace/github/macwire/examples/play24/app/com/softwaremill/play24/AppApplicationLoader.scala:31: Cannot find a value of type: [String]
[error] lazy val router: Router = wire[Routes] withPrefix "/"
[error] ^
[error] two errors found
[error] (compile:compileIncremental) Compilation failed
It seems that macwire 2.0
- recognizes overridden (abstract) member as another value
- does not take secondary constructors into account (even if it's annotated with
@javax.inject.Inject())
Hi guys, do any of you have encountered issues play logging and macwire?
If I use this example: https://github.com/adamw/macwire#play24x, logging get muted
If I use this example: https://github.com/adamw/macwire#play24x, logging get muted
I don’t think the problem resides in macwire, but in extending Play’s ApplicationLoader
My impression is that somehow the logging configuration won't be loaded
My impression is that somehow the logging configuration won't be loaded
when using macwire with play, make sure you configure the logging as such:
class AppApplicationLoader extends ApplicationLoader {
def load(context: Context) = {
Logger.configure(context.environment)
(new BuiltInComponentsFromContext(context) with AppComponents).application
}
}
without that you’ll get nothing in your logs
will send a PR to the README file and example/play24
will send a PR to the README file and example/play24
I'm wondering what are some tried good practices macwire users apply to pass configuration properties during wiring
so a regular type :)
I have a question about using Play+Macwire+Akka
How can I inject Play's ActorSystem with macwire?
in documentation they says "import play.api.libs.concurrent.Akka"
it is works, but not with Macwire...
Actually it is working now :)
import play.api.Play.current
import play.api.libs.concurrent.Akka
trait ActorsModule {
lazy val actorSystem = Akka.system
}
this module is fine. The problem was here
object Global extends GlobalSettings with Macwire {
val wired = wiredInModule(Application)
override def getControllerInstanceA = wired.lookupSingleOrThrow(controllerClass)
}
I made wired lazy and all goes fine :)
so it was the initialization order
common with lazy vals :)
I can't write like this:
class PostgreDatabase(dbPoolActor: ActorRef)
because I have more than one Actors in my system that I want to inject
class PostgreDatabase(dbPoolActor: ActorRef)
because I have more than one Actors in my system that I want to inject
Looks like I should use tags
I have:
import play.api.Play.current
import play.api.libs.concurrent.Akka
trait ActorsModule {
lazy val actorSystem = Akka.system
lazy val dbPoolActor = actorSystem.actorOf(Props(wire[DBPoolActor])).taggedWith[DBPoolActor]
}
and DB
class PostgreDatabase(dBPoolActor: ActorRef @@ DBPoolActor) extends Database { ...
}