So it seems some of the documentation has become stale in the post-Scala.JS-1.0-world, @arminio it'd be really appreciated if you would kindly submit a PR, or even an issue with a list of changes you had to make, so that we can update the doc for future users.
And sorry you bumped into a few problems. Glad to hear you got it sorted out
Should I simply tag my test-state questions with
scalajs-react?
So it seems some of the documentation has become stale in the post-Scala.JS-1.0-world, @arminio it'd be really appreciated if you would kindly submit a PR, or even an issue with a list of changes you had to make, so that we can update the doc for future users.
@japgolly PR for a small update to the test-state documentation raised:
japgolly/test-state#144
Is there any way to make that work?
Because of the way it works it seems like the second setState essentially overrides the first
Is there a way to decompose and then recompose state-setting like that?
@japgolly Hi I have been working so far with slinky, I have created a project with some examples of hooks. now I would like to know how to write custom hooks using scalajs-react. Any example using useMemo, useContext or useRef without declaring components? Here my example in Slinky.
Oh my bad I didn't realise you were using the parameter. In that case, you've got two options: (1) exactly what you wrote above, (2) use
CallbackKleisli and then call .toJsFn. (1) is nice and simple and (2) is a great option if you're doing lots of composition but in many cases it's likely to just be over-engineering for no benefit so you'll have to access your situation and choose whichever's best. Hope that helps
have anyone tried to update to reactjs 1.7.0? https://reactjs.org/blog/2020/10/20/react-v17.html not sure if scala.js react will just work with it
Hi @japgolly, I'm currently using scalablytyped definitions with react-window. Their constructor for the FixedSizeList component was translated as following:
object FixedSizeList {
// ...
def apply(
children: ComponentType[ListChildComponentProps],
height: Double | String,
itemCount: Double,
itemSize: Double,
width: Double | String
) { ...}
// ...
}where ComponentType is:
type ComponentType[P] = (japgolly.scalajs.react.raw.React.ComponentClassP[P with js.Object]) | typings.react.mod.FunctionComponent[P]I've been trying to pass in a simple component and no matter what I try I can't get it to compile.
The closest I've got was this:
val comp = ScalaComponent.builder[ListChildComponentProps]("a").render_P { x => <.div("foo") }
Window.FixedSizeList(height = 800, width = 800, itemSize = 200, itemCount = 42,
children = ViaReactComponent(comp))But then it returns boxed props and states so a mismatch again.
Any pointers on how I could get this to work?
@tom91136 there's a fairly high chance that
ComponentType is not the perfect type here, I haven't given this pattern much thought. Tell me if you find something better. The important thing is that what's taken as children here is the javascript version of a component, I'm fairly sure there is a way to go from a scala component to a js component
@oyvindberg From what I can see, the original TypeScript definition (https://github.com/DefinitelyTyped/DefinitelyTyped/blob/fb606b70c8e67c4078b6eecec9ebf13918778002/types/react-window/index.d.ts#L119) is directly translated by the scalablytyped plugin.
I've tried pretty much everything on the interop page but the types just don't seem to match up. If I cast it then I get a ClassCastException
Hello all! Venturing into using Test-State for an sjs-react app ... question @japgolly , I have a component that async loads another element into the page and I want to test that it indeed (eventually) exists. I'm using JS side tests so it looks like I cannot use
Test.withRetryPolicy(policy) Is there another option?
@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