You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The former is entirely comprised of inlines, I think its place should be in the WIG definition. This would also make it more consistent to use from C#, instead of separate JS and JSModule.
The only non-trivial part of this would be moving AnimationFrameResource, which is not a simple BaseResource and therefore can't be defined in WIG. I guess it would have to be defined in WS.Core.
The text was updated successfully, but these errors were encountered:
The part of JS that is currently defined in the WebSharper.JavaScript assembly is just functions that are, in js, defined on the window object, plus Inline which is a WebSharper construct. So what we should do is:
Ensure that these functions are defined on the Window proxy.
Define aliases for them in the module WebSharper.JavaScript.JS in the WebSharper.Main assembly.
Remove the class WebSharper.JavaScript.JS from the WebSharper.JavaScript assembly.
The former is entirely comprised of inlines, I think its place should be in the WIG definition. This would also make it more consistent to use from C#, instead of separate JS and JSModule.
The only non-trivial part of this would be moving
AnimationFrameResource
, which is not a simpleBaseResource
and therefore can't be defined in WIG. I guess it would have to be defined in WS.Core.The text was updated successfully, but these errors were encountered: