Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 10:57
  • Jan 30 2019 22:22
    bitpirate starred japgolly/scalajs-react
  • Jan 30 2019 08:11

    japgolly on master

    Update docs for changes in 1.4.0 (compare)

  • Jan 29 2019 13:20
  • Jan 28 2019 08:08
    booleguo starred japgolly/scalajs-react
  • Jan 28 2019 04:09

    japgolly on v1.4.0

    (compare)

  • Jan 28 2019 04:05

    japgolly on master

    Towards v1.4.1 (compare)

  • Jan 28 2019 04:04

    japgolly on master

    Prepare for v1.4.0 Upgrade React to 16.6.3 React.lazy and 85 more (compare)

  • Jan 28 2019 04:04
    japgolly closed #521
  • Jan 28 2019 04:04
    japgolly opened #521
  • Jan 28 2019 04:03

    japgolly on v1.4.x

    Add note about Reusability/Reus… doc formatting Prepare to release v1.4.0 (compare)

  • Jan 28 2019 04:02
    wiitht starred japgolly/scalajs-react
  • Jan 28 2019 03:18

    japgolly on v1.4.x

    Test AsyncCallback.init Update Travis CI caching (compare)

  • Jan 28 2019 03:02

    japgolly on v1.4.x

    Update Travis CI cache dirs Revise changelog (compare)

  • Jan 28 2019 03:00
    japgolly labeled #520
  • Jan 28 2019 03:00
    japgolly labeled #519
  • Jan 27 2019 17:36
  • Jan 26 2019 06:49
    japgolly commented #520
  • Jan 26 2019 05:55
    japgolly commented #519
  • Jan 26 2019 02:35
    cquiroz opened #520
Øyvind Raddum Berg
@oyvindberg
@tom91136 exactly :)
nafg
@nafg
1.7.6 dropped support for sjs0.6 intentionally?
Ryan Richt
@ryan-richt
bah, and sadly it appears ReactTestUtils.actAsync is not implemented for the scalajsreact node env (requires MessageChannel so throws a deep react error) so that's not the solution either...
nafg
@nafg
Turns out it was unintentionally not published, and David now published it
Tom Lin
@tom91136
@oyvindberg PR ScalablyTyped/ScalaJsReactDemos#6 sent
Roberto Leibman
@rleibman
Hi @oyvindberg , it's been a while, I'm refreshing my projects. I don't have a lot of time to move from apply methods to the builder style, so I'm using the stEnableLongApplyMethod variable, but the apply methods are not being generated.
Roberto Leibman
@rleibman
This is my project, btw: https://github.com/rleibman/chuti
Øyvind Raddum Berg
@oyvindberg
I'll have a look @rleibman :)
Roberto Leibman
@rleibman
Thanks!
Øyvind Raddum Berg
@oyvindberg
@rleibman never generated nor just not in a few cases?
Roberto Leibman
@rleibman
I'm only using Semantic ui in this particular project, as far as I can tell, all of 'em
Øyvind Raddum Berg
@oyvindberg
@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)
Roberto Leibman
@rleibman
Thank you!
Roberto Leibman
@rleibman
@oyvindberg haha, sorry, I should have posted this in the ScalablyTyped channel, I saw your name mentioned here and I thought that was it. Anyway, that worked, thanks again, and I promise I'll get around to changing to use Builders
BTW, the "key" parameter is not coming through. I know that one is a special thing.
Valentin Willscher
@valenterry
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?
nafg
@nafg
I am very much in favor of that
Valentin Willscher
@valenterry
Wonder what @japgolly thinks about it
nafg
@nafg
@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
Valentin Willscher
@valenterry
I commented on the PR, thank you!
Denis Porfiryev
@justdanpo
Hello. Is it possible to use render*C (receiving children) together with configure(EventListener?
Denis Porfiryev
@justdanpo
What is the correct way to iterate over two refs?
Denis Porfiryev
@justdanpo

Hello. Is it possible to use render*C (receiving children) together with configure(EventListener?

Ok, I've solved this one: all I needed was backend extending OnUnmount

Matt Hughes
@matthughes
What versions are folks using along with SJS React? Still using 2.12? Still using SJS 0.6?
Thoughts on dropping those two axes in favor of 2.13/3.0 and 1.3+?
nafg
@nafg
That's definitely going to happen soon IMO
Matt Hughes
@matthughes
Support 2.13/3 is hard enough; I can’t imagine trying to support all three. And by the time 3 is actually done and ready, it will be probably at least a few months.
I’m sure there’s a way to look at the download stats for 2.12
Todd Burnside
@toddburnside
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?
Øyvind Raddum Berg
@oyvindberg
@toddburnside do you have a typescript example of what you're trying to do? I believe you'll have to drop beneath the surface a bit for this, but it shouldn't be that hard
Todd Burnside
@toddburnside
@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().
Todd Burnside
@toddburnside
For future generations who stumble across this, see issue #837 for the answer.
Matthew de Detrich
@mdedetrich
Hey so I am migrating from an ancient version of scalajs-react (0.11.5) to the newest version (1.7.7) due to having to update to Scalajs 1.3.4. I have gone through and migrated everything but there is this one last problem I am having

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
      })
      .build

However 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?
Matthew de Detrich
@mdedetrich
Note that I have already updated the ReactComponentB to ScalaComponent.builder
Matthew de Detrich
@mdedetrich
I just realized this is a generic react question so I will ask in the appropriate channels
Yilin Wei
@yilinwei
@mdedetrich if you don't mind me asking, what was the answer?
Matthew de Detrich
@mdedetrich
Sorry for the late reply
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
Antonio R. Rodríguez Santiesteban
@rodant

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.

Antonio R. Rodríguez Santiesteban
@rodant
Ok, problem solved by using removeLeadingSlashes as first Rule.
jhegedus42
@jhegedus42
I am upgrading now everything I can and I get lots of linking errors from scalajs-react-bridge
image.png