Hi Collin,
Thanks for your answer, I understand now, I was only focusing on my problem
and forgot the JS to Java way. As you say, something cool would be to be
able to say to JsInterop that the interface will only be used in the Java
to JS way...
Thanks!
Le sam. 27 août 2016 16:13, Colin Alworth
Part of the problem would come from figuring out how to call from JS back
into Java - if you called resolve(null), was null a T or was null a
Promise? And from JS, how could you typecheck to figure out whether to call
the resolve_1(value) or resolve_2(promise)?
Its also possible in JS to call
Hi,
I am playing with js Promises and maybe there's a problem with JsInterop or
i don't understand something.
When wrapping the promises with JsInterop, i come to define the Resolver
interface which represents the resolving callback that is given when
constructing a promise. In Javascript it
Em... this is kind of related, some days ago I speak about this with manolo
in gitter; currently the CodeServer use the standard nocache.js instead of
the compile-on-refresh (actually uses the compile-on-refresh the first
time, but subsequent compilations uses the standard one). And... does not
