Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid types in RPC signature does not fail at compile time #989

Jand42 opened this Issue Jul 16, 2018 · 0 comments


None yet
2 participants
Copy link

Jand42 commented Jul 16, 2018

Whenever using a class that is not appropriate for RPC argument or result (for example it is a delegate or a class with no default constructor), no compiler error is given, only at server runtime, when RPC handler tries to deserialize an object. RPC result is also too allowing, for example an F# function object is allowed to be returned, but will be seen on the client as an empty JS object (failing to be called at client runtime).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
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.