@rleibman the
stEnableLongApplyMethod mechanism wasn't implemented for react flavours. I added it here ScalablyTyped/Converter@a28e107 (along with a note that it's deprecated)
BTW, the "key" parameter is not coming through. I know that one is a special thing.
I'm work more and more with scalajs-react and it seems really huge. I wonder if there are thoughts to split it into a core, which would just be a Scalajs API for react and then a separate module with a DSL for easy component creating, a module with a router if one does not want to use react-router and so on. Thoughts?
@valenterry comment on japgolly/scalajs-react#488. A lot has happened since then -- that was before ScalablyTyped (its predecessor was not so great)
Also scala-dom-types has been around for a while now
Although I'm not sure if you are asking for the same exact thing
Also when he replied "I don't see this happening" I'm not sure if he meant "I don't have the motivation to do this myself" or "I don't want this to happen even if someone else does the work." (Either way his opinion may have changed since then.)
So either chime in on that ticket, or open a new one
Thoughts on dropping those two axes in favor of 2.13/3.0 and 1.3+?
I’m sure there’s a way to look at the download stats for 2.12
Hi all. We have created a facade for ag-grid-react using ScalablyTyped. The basic functionality is working fine, but the grid allows for things like custom cell renderers and cell editors to be specified as react components. I am able to pass in components using either a function as described in INTEROP.md or with
component.cmapCtorProps[…](…).toJsComponent.raw. However, the grid requires some extra “lifecycle” functions to be available on some of the components, such as getValue(): js.Any, which the grid uses to get the new value after editing is completed. I was hoping that if I put the functions in the Backend of the component, they would be visible to the grid. But, no matter what I try, I get this helpful message in the console: “ag-Grid: Framework component is missing the method getValue()”. Is there a way to make extra functions in a component visible to the grid?
@oyvindberg I don’t have a typescript example, but there is a jsx example here: https://github.com/ag-grid/ag-grid-react-example/blob/master/src-examples/richGridDeclarativeExample/NameCellEditor.jsx They are just declaring the functions the grid will call, such as
getValue(), right alongside render().
Previously I had
val App =
ScalaComponent.builder[MainProps]("First")
.initialState(basicMainObject)
.renderBackend[Backend]
.componentWillUpdate(update => {
if ((update.nextProps != update.currentProps) && (update.nextProps.input != js.undefined)) {
update.backend.scan(update.nextProps.input.getOrElse(""))
} else Callback.empty
})
.buildHowever the issue is that componentWillUpdate is now deprecated. I am trying to use componentDidUpdate however I have no reference to nextProps.
Is it that the old
currentProps is now prevProps and the old nextProps is now currentProps?
But it was basically what I suggested
i.e.
Is it that the old currentProps is now prevProps and the old nextProps is now currentProps?
@yilinwei
Hi here, I'm having also issues migrating from 1.4.2 to 1.7.7, router errors like:
"Multiple (2) (unconditional) routes specified for path #explorer?iri=https://ochun1.inrupt.net/"
and I don't grasp why. Here is the code:
`
sealed trait AppPage
case object Home extends AppPage
case class Explorer(iri: String = IRI.BlankNodeIRI.toString) extends AppPage {
lazy val dirIri: String = IRI(if (iri.endsWith("/")) iri else s"$iri/").normalize.toString
}
private val config = RouterConfigDsl[AppPage].buildConfig { dsl =>
import dsl._
(trimSlashes
| staticRoute(root, Home) ~> render(SPOTBox.Page(IRI.BlankNodeIRI.toString))
| dynamicRouteCT[Explorer]("#explorer?iri=" ~ string(".+").caseClass[Explorer]) ~> dynRender(p => SPOTBox.Page(p.dirIri)))
.notFound(redirectToPage(Home)(SetRouteVia.HistoryReplace))
.renderWith(layout)}`
thanks for any hints in advance.
here is the code : https://github.com/jhegedus42/im2020
val scala = "2.12.10"
val scalaJSDom = "1.1.0"
val scalajsReact = "1.7.7"
val scalaCSS = "0.6.1"
val kinoplan = "0.2.1"
val akka = "2.5.23"
val akkaHttp = "10.1.9"
val monocleVersion = "2.0.0"
val scalaTestVersion = "3.0.8"
and related imports:
"com.github.japgolly.scalajs-react" %%% "core" % versions.scalajsReact,
"com.github.japgolly.scalajs-react" %%% "extra" % versions.scalajsReact,
"com.github.japgolly.scalacss" %%% "ext-react" % versions.scalaCSS,
"com.github.japgolly.scalacss" %%% "core" % versions.scalaCSS,
"com.github.japgolly.scalacss" %% "ext-scalatags" % versions.scalaCSS,
"org.scala-js" %%% "scalajs-dom" % versions.scalaJSDom,
"com.payalabs" %%% "scalajs-react-bridge" % "0.8.2",
"org.scalatest" %%% "scalatest" % versions.scalaTestVersion % "test",
"io.kinoplan" %%% "scalajs-react-material-ui-core" % versions.kinoplan,
"io.kinoplan" %%% "scalajs-react-material-ui-icons" % versions.kinoplan,
"io.kinoplan" %%% "scalajs-react-material-ui-lab" % versions.kinoplan
any ideas where to start debugging this ?
it compiles just fine
