WebSharper 2.5.127 released

Andras Janko

Andras Janko

Oct 09, 2014

Reading time:

1 mins

Share via:

Additions to RPC functionality

Map and Set types are now usable in RPC functions.

If you are returning these to client side, be sure that the type of the set elements or map keys have the same comparison logic the server and client side, or else it can lead to unexpected behavior as the returned collection is not re-sorted. However, you don't have to worry about this if you don't explicitly overload the CompareTo method with a JavaSript Inline working differently than the method body running in .NET.

Bugfixes

  • A compile error is given if a non JSON-encodable type is used in an RPC signature.
  • Date.now and the Async scheduler now works on IE8.
  • No more deprecated warning about using nodeValue.
  • In WIG, T<SomeGenericType<_>>.[YourTypeDefinition] now translates properly to indicate the type SomeGenericType<YourType>.

Read more from

Can’t find what you were looking for? Drop us a line.

Andras Janko
Found a typo?

This blog post is hosted on GitHub here. Feel free to file a ticket or send a PR.

Newsletter

We will not spam you or give your details to anyone.