TS-client outstanding work

[moozzyk]

As per davidfowl/Sockets#12

• add transport closed event (33c94c1)
• remove fallback as per discussion today (325c909)
• figure out modules (2039a18)
• unify errors (33c94c1, 913354f)
• review capturing of this in callbacks/eventhandlers (b32d3ad)
• logging tracked now as: Consistent, configurable logging in the JavaScript client #485
• convert RpcConnection to HubConnection (e6b34fd)
• detach dispatching from transports/connection (70e4ec9)
• enable plugging in custom formatters (The Hub protocol needs framing #12)
• split messages (Occasionally getting split messages in ChatSample #6)
• joined messages (especially important for longpolling - multiple messages in one poll response) (78dfd27)
• is there a better way of bringing typings for EventSource (currently we have them in the repo: 02c9813)
• tests
• consider using async/await (requires typescript 2.1.1?) (3a01d6c)
• handle cases where a method called from the server does not exist on the client
• hubConnection needs error event (2bbca5e)
• review usages of httpClient. It shouldn't be created each time it is needed and it should be possible to provide alternate implementations (e.g. for mocking) (a9c7e14)
• try using IHttpClient for polling
• don't build the client multiple times when running build.cmd (after moving to MSBuild) (0162c19)
• create typescript VS projects so that they show up in VS (0162c19)
• ccabbbc#commitcomment-20536735

[valeriob]

Hi, what do you think about compiling the ts client when you build the library and publish the .js and .d.ts files as a package ? I do not see any real advantage on pushing this added complexity on the users of the library :D

Ps: right now i can't figure it out how to use the ts client on my project, i would love to give it a try

[moozzyk]

@valeriob - we want to do something to that effect but so far have been working on functionality rather than release story. If you want to use the client at the moment now you can clone the repo run build.cmd/build.sh and copy the client to your project from the artifacts/lib folder.

[valeriob]

Thanks @moozzyk i understand priorities, i'm glad it's in the radar :D
I'll do as you said !

[MarkPieszak]

@moozzyk Excellent work! Didn't know work was already underway to support vanilla JS already :)
I'd love to get involved and help with this, can you let me know any specific things I can work on to finish everything up?

I'm on the .NET Core slack (aspnetcore.slack.com) if you want to ping me on there as well.

[davidfowl]

Opening smaller issues since a bulk of the work is done here.