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
With the changes on #853, the client function in back-compatibility package WebSharper.UI.Next is broken unless the old logic for looking up a single call to a static method from a quotation is restored as a fallback if no pre-compiled form of the quotation exists.
Also, uses of ClientSide always create a new generated JavaScript function for the expression (on current master), even if it is a single call to a static method which was the only form allowed in 4.0. By excluding these from pre-compilation with a simple pattern match, the fallback would work for them as before, resulting in no extra code that is just doing redirection.
The text was updated successfully, but these errors were encountered:
There is an unnecessary error thrown when a JavaScript argument is not quotation literal. Now the fallback can handle dynamic quotations again, if they are containing a call to a single static method. Also, in UI we need to pass along a quotation value in the client alias for Doc.ClientSide.
With the changes on #853, the
client
function in back-compatibility packageWebSharper.UI.Next
is broken unless the old logic for looking up a single call to a static method from a quotation is restored as a fallback if no pre-compiled form of the quotation exists.Also, uses of
ClientSide
always create a new generated JavaScript function for the expression (on currentmaster
), even if it is a single call to a static method which was the only form allowed in 4.0. By excluding these from pre-compilation with a simple pattern match, the fallback would work for them as before, resulting in no extra code that is just doing redirection.The text was updated successfully, but these errors were encountered: