mergify[bot] on master
Update scalafmt-core to 3.5.9 (… (compare)
github-actions[bot] on gh-pages
Deploying to gh-pages from @ ou… (compare)
mergify[bot] on master
Update scalatest to 3.2.13 (#63… (compare)
mergify[bot] on master
Update scalatest to 3.2.13 (#64) (compare)
mergify[bot] on master
Update sbt-mdoc to 2.3.3 (#635) (compare)
github-actions[bot] on gh-pages
Deploying to gh-pages from @ ou… (compare)
not found: type Handler
[error] def cmpDate(hdl: Handler[Long]) =
import outwatch.reactive.handler.Handler
import outwatch.reactive.handlers.monix._
Handler
. To me, this concept feels too complex, that you indirectly create new instances of your stream-types (just with the help of a magic import). It just seems more straightforward to directly create your subjects with the library of your choice. The intent is much more clear.Observable
in your dom nodes.any idea why this code works perfectly, but if I put the class FrmClass
on another file it doesn't?
class TestingOnClassSpec extends JSDomAsyncSpec {
class FrmClass {
val testClick = new Observer[String] {
def onNext(elem: String): Future[Ack] = {
Future {
println(elem)
Continue
}
}
def onError(ex: Throwable): Unit = { println(ex.printStackTrace.toString) }
def onComplete(): Unit = println("O completed Handler")
}
val but = button( idAttr := "cmdTestOnClass", "Save", cls := "myButton",
onClick.use("on the observer a class ----------") --> testClick
)
}
it should "be test the save button" taggedAs(ButtonTestingTest) in {
val frm = new FrmClass
for {
_ <- OutWatch.renderInto[IO]("#app", frm.but)
} yield {
val element = document.getElementById("cmdTestOnClass")
sendEvent(element, "click")
succeed
}
}
}
something lacking me ?
VNode
. The element is what you can append the canvas to which is rendered by nspl.