Everything about Slinky -- issues, ideas for features, where it's being used, and more
:= (evt) => keyHandler(evt)? Slinky uses a bit of implicit trickery in order to have the event's element type match the tag that the attribute is being applied to, I wonder if there's some issue with partially applied functions here. You are setting this attribute on an input tag, right?
Hi all. Thoroughly enjoying Slinky to build my app using functional components with hooks. I've hit a road block with useContext in that I can't figure out how to set the value. I naively thought it would be similar to useState like so:
val (thing, setThing) = useContext(MyContexts.thing)which I believe is how it works in vanilla React. This doesn't appear to be the case with Slinky (version 0.6.5). Could someone please explain how to use context with functional components in Slinky? What have I misunderstood? Thanks!
It doesn't seem to provide a way to set the context from the result of the
useContext hook. Note that React doesn't do this either: https://reactjs.org/docs/hooks-reference.html#usecontext You set the context using a Provider.
MyContexts.thing.Provider approach within the functional component that sets the value and render all consumers of that value within the body of that provider.On a slightly related note, is there a recommended/efficient way of sharing state globally?
Hey there; loving this library so far!
I am running into an issue with the react-router facade when trying to use activeClassName with NavLink. I'm not sure why, since I think I'm using it the same way NavLink is used for the sidebar on the Slinky docs site, and that works perfectly.
Minimal example of what isn't working for me:
@react object Homepage {
case class Props()
val component = FunctionalComponent[Props] { props =>
NavLink(
to = "/about",
activeClassName = Some("bar")
)(
className := "foo"
)(
"About"
)
}
}
ReactDOM.render(
Router(
history = History.createBrowserHistory()
)(
Switch(
Route("/", Homepage.component, exact = true),
Route("/about", Homepage.component),
Route("*", Homepage.component)
)
),
container
)The link itself works, and goes to the /about page, but the bar class doesn't get added when /about is the current page.
Any thoughts on what I might be doing wrong would be greatly appreciated!
On a slightly related note, is there a recommended/efficient way of sharing state globally?
@mn98 not sure if it can be of interest in your search, but I wrote this example about using Diode https://github.com/mcallisto/slinky-diode-todomvc
I'm having troubles to translate this to slinky external components, the official docs has no similar example, any hint is appreciated: http://recharts.org/en-US/guide/getting-started
The js side is:
import { LineChart, Line } from 'recharts';
const data = [{name: 'Page A', uv: 400, pv: 2400, amt: 2400}, ...];
const renderLineChart = (
<LineChart width={400} height={400} data={data}>
<Line type="monotone" dataKey="uv" stroke="#8884d8" />
</LineChart>
);Hello @shadaj, I have the following question.
Is there a drier or more idiomatic way in Slinky to achieve the following:
def toOption[T](ot: T | Null): Option[T] = Option(ot.asInstanceOf[T])
var swi: Option[ScrollViewInstance] = None
val scrollView = ScrollView().withRef(nullableRef => swi = toOption(nullableRef))
swi.head.scrollToEnd()That is, using the scrollToEnd method of the slinky.native.ScrollView component?
@react style? Currently the docs suggest this isn't supported. This would help me consolidate quite a bit of duplicate code in the future. I can work around it for now, was just curious, thanks!
Looks like this SBT setting controls it: https://github.com/scalacenter/scalajs-bundler/blob/975a04812334fd4241dbfdcc76a0e511a71b6585/sbt-scalajs-bundler/src/main/scala/scalajsbundler/sbtplugin/ScalaJSBundlerPlugin.scala#L411
Something like
webpackDevServerPort := 8000in build.sbt should do it.
toOption a bit by adding T <: AnyRef, which should eliminate the need for the cast; unfortunately not much more that can be improved, but perhaps useRef could simplify the code a bit?
0.6.5, but I can't get it to work with 0.6.6. I've tried using the version numbers 0.6.5+31-43e32880, 0.6.6, 0.6.6+1-83a94445, and 0.6.6+4-7d07b9a5 for the ijext Maven artifact with Slinky 0.6.6, but I only get a prompt to enable the extension with Slinky 0.6.5 and artifact version 0.6.5-*. I don't get the prompt that's supposed to come up according to the docs with either version of Slinky. Is this something wrong with my machine, or have others also not been able to use the IntelliJ extension with 0.6.6? (Also, I'm on IntelliJ 2020.1.1, but the problem showed up for me on 2020.2.2 as well)
0.6.5+15-fa93d141; before, the IntelliJ plugin was published under the name slinky-core-ijext_2.12 (and 2.13) but after that it's only been published under slinky-core_sjs0.6_2.12 (and 2.13)
1 reply
I don't know if this is a Slinky or ScalablyTyped question but I tried to get React Monaco Editor component to work and yes it works but I have to construct it with "ReactMonacoEditor.withProps(MonacoEditorProps().set("height", "500").set("width", "500"))"
Why? Is there a more normal way to construct it?
I made demo project here https://github.com/PhilAndrew/ReactSlinkyScalablyTyped
With the file of that code here https://github.com/PhilAndrew/ReactSlinkyScalablyTyped/blob/master/react-leaflet/src/main/scala/demo/App.scala
