A quick fix would be, in a linker, to substitute "new $wnd.Object"
with "{}". It's possible to write a peephole pass to fix this in the
Compiler, but I think given the number of people clamoring for GWT 2.8
and the other more pressing issues, this would be low on the totem
pole.
On Sun, May 1,
On Sunday, May 1, 2016 at 5:46:26 PM UTC+2, Jens wrote:
>
> Depending on what exactly you want to test I would try hard using plain
> JUnit with mocking / stubbing. Testing @JsType(native = true) annotated
> interfaces / classes probably does not make a lot of sense given that the
>
Depending on what exactly you want to test I would try hard using plain
JUnit with mocking / stubbing. Testing @JsType(native = true) annotated
interfaces / classes probably does not make a lot of sense given that the
underlying JS code should already be tested and given that GWT itself has
What is the best way to unit test JsInterop code? Am I correct that
GWTTestCase doesn't work?
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
When you define an object literal as
@JsType(isNative = true, namespace = JsPackage.GLOBAL, name="Object")
public class SomeObjLiteral {
}
Calling new on this results in the following javascript code 'new $wnd.Object'.
You could just emit {} instead.
It is surprising the number times you
I am trying to create a native JsType to represent a javascript Array. Up
to this point I have been using JSNI. Below is the outline of what I have.
I want to use an Interface as my eventual goal is to be able to define JSON
structures using the same class on client and server.
