Report compile error when can't encode/decode RPC args/result

[intellifactory-bb]

Previously wrongly typed RPC arguments reported a warning, result haven't.

---

• Bitbucket: https://bitbucket.org/intellifactory/websharper/issue/289
• Originally reported by: András Jankó
• Originally created at: 2014-09-24T11:22:33.622

[intellifactory-bb]

fix #289: give compile error on non-encodable type in RPC

→ <<cset 80c9da18ad31>>

---

Original comment by: András Jankó

[V0d01ey]

Now if an argument/result-class don't have a default constructor the analyzer don't report a warning.
Should I open a new issue? Or this issue can be reopened?

[Jand42]

@V0d01ey Not even compilation fails? I will check this. The C# analyzer is not doing the RPC signature verification right now as it needs reflection (possibly this will change if RPC/and sitelets json behavior are unified).

[V0d01ey]

@Jand42 , yes, the error reveals itself by crash only when you try to send such object (not null) from client to server. And inside complex structure it is not trivial to locate the problem.

[Jand42]

@V0d01ey Thanks for the report! I have created ticket #989.