oyvindberg on gh-pages
Deploy website Deploy website … (compare)
oyvindberg on v1.0.0-beta29.2
oyvindberg on v1.0.0-beta29-patch
Update ammonite-ops to 2.3.8 Update sbt-mdoc to 2.2.13 Better error logging in CI and 12 more (compare)
oyvindberg on gh-pages
Deploy website Deploy website … (compare)
oyvindberg on master
Update sbt-mdoc to 2.2.15 (compare)
oyvindberg on master
Update library-developer.md Ad… (compare)
oyvindberg on scala-companion-objects
oyvindberg on scala-companion-objects
Generate more specific types fo… (compare)
oyvindberg on v1.0.0-beta29.1
oyvindberg on v1.0.0-beta29-patch
Another bugfix for remote cache (compare)
oyvindberg on gh-pages
Deploy website Deploy website … (compare)
oyvindberg on master
Restore compatibility with old … (compare)
oyvindberg on master
Restore compatibility with old … (compare)
oyvindberg on master
Another bugfix for remote cache (compare)
oyvindberg on master
Reintroduce `^` classes (compare)
oyvindberg on gh-pages
Deploy website Deploy website … (compare)
oyvindberg on master
add scalablytyped icon (#235) … (compare)
oyvindberg on master
try to speed up CI (compare)
oyvindberg on improve-class-extraction
oyvindberg on master
Improve ExtractClasses and Reso… (compare)
data
attribute to charts?
typings
, have you set https://scalablytyped.org/docs/conversion-options#stoutputpackage ? If so that's where you'll find the scala code. Also if you picked SourceGenMode.Manual
you need to run the stImport
task once
DataGrid
component, but seems it's not possible with the current supported version of MaterialUI?
dotty-support
branch?
js.Object
are just a description of a Javascript object, and that's a convenient way to create them.
Hi @oyvindberg , could you clarify the setting of stReactEnableTreeShaking
. The docs say "Enable this ... to prefer react components in long module paths..." and "The difference in bundle size can be remarkable, for instance the Slinky material-ui demo ended up one fifth of the original size." And in code, its default value is Selection.None
.
I take that as it's recommended that we do not normally want to enable stReactEnableTreeShaking
by setting it to anything other than Selection.None
. Is that correct?
stReactEnableTreeShaking
is actually an amazing feature which does that whole pass for all ST react dependencies you use!
withComponent
method or whatever I called it where you can supply an implementation imported from a more specific import)
withComponent
imports. If you can give me an example import (for withComponent
), that'd be great.
stReactEnableTreeShaking
first
How should something like:
export interface SourceMapConsumerConstructor {
prototype: SourceMapConsumer;
new (rawSourceMap: RawSourceMap, sourceMapUrl?: SourceMapUrl): Promise<BasicSourceMapConsumer>;
new (rawSourceMap: RawIndexMap, sourceMapUrl?: SourceMapUrl): Promise<IndexedSourceMapConsumer>;
new (rawSourceMap: RawSourceMap | RawIndexMap | string, sourceMapUrl?: SourceMapUrl): Promise<BasicSourceMapConsumer | IndexedSourceMapConsumer>;
}
export const SourceMapConsumer: SourceMapConsumerConstructor;
be converted? It is being converted to:
@js.native
trait SourceMapConsumerConstructor
extends Instantiable1[
(/* rawSourceMap */ RawIndexMap) | (/* rawSourceMap */ RawSourceMap) | (/* rawSourceMap */ String),
js.Promise[BasicSourceMapConsumer | IndexedSourceMapConsumer]
]
with Instantiable2[
(/* rawSourceMap */ RawIndexMap) | (/* rawSourceMap */ RawSourceMap) | (/* rawSourceMap */ String),
/* sourceMapUrl */ SourceMapUrl,
js.Promise[BasicSourceMapConsumer | IndexedSourceMapConsumer]
] {
}
@JSImport("source-map", "SourceMapConsumer")
@js.native
object SourceMapConsumer extends TopLevel[SourceMapConsumerConstructor]
In TypeScript I could do:
new SourceMapConsumer(sourceMap)
(SourceMapConsumer: SourceMapConsumerConstructor).newInstance1(json)
SourceMapConsumerCls
next to it in the library
typings.std.Promise
? Couldn’t it just use scala.scalajs.js.Promise
?
js.Promise
, as long as they don't form part of inheritance (because that opens up a lot of problems for reliably generating code). There is also an edge case where references to std.Promise
in overloaded methods won't be translated, because it might cause compilation to fail because different methods might end up with same erasure