dotnet/aspnetcore

"stateChanged" missing from Typescript SignalR lifetime events?

Open

#17,900 opened on Dec 16, 2019

View on GitHub
 (9 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
affected-very-fewapi-suggestionarea-signalrenhancementhelp wantedseverity-minor

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 9d 17h) (156 merged PRs in 30d)

Description

Describe the bug

onreconnecting, onreconnected, onclose, and the event from start() are the only ones supported currently in the Typescript client, is this correct?

To Reproduce

Attempt to use stateChanged ..

Further technical details

SignalR for Typescript version 3.1.0.

Contributor guide

Research direction
Search for existing lifecycle event definitions in the TypeScript client code, likely in a file like 'IHubConnection.ts' or 'HubConnection.ts', and add the 'stateChanged' event similar to the .NET client.
Tech stack
typescriptcsharp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptSignalR
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60