As I get reacquainted with SignalR via SignalR Core, I've found that a lot of the lifecycle operations are no longer supported. It'd be nice to have a page for SignalR Core that outlines some of the connection lifecycle operations as well as some best practices like there is for ASPNET SignalR.
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@docrinehart Thanks for the suggestion. I agree, and while I can't predict how soon we'll get to it, it's on our backlog now.
@bradygaster please review and schedule
@Rick-Anderson assigning the new-and-awesome SignalR label so we can triage these during our regular team triage.
closing as this feels like a dupe of #6757 so we'll handle it there.
@bradygaster You closed #6757 a few weeks ago with the comment:
closing this as a duplicate of #9280, which would represent a superset of the desires of this particular issue.
Then closed this ticket yesterday as a duplicate of that one. At a glance I don't see that any documentation was crafted for either ticket, so I want to ask if the ticket reference here was incorrect (maybe a typo) and make sure we eventually get some docs around the signlar core lifecycle events.
Thanks for calling me out on that. It was an oversight. We absolutely want to complete the work for this issue, #9280. My apologies, I'll re-open this one.
@guardrex - @bradygaster wants to know if you could look into writing this doc because you're the best. Thanks!
Thanks for the complement.
I'm not a SignalR :cat2: ... I've never used it. I can possibly write it if I get on the learning curve with SignalR. Timing is a bit of a challenge tho: I have 3.0 issues to resolve, (light) Blazor demands, and I hope to retire ... mostly retire anyway ... in December. 🏖
No worries. Worth a shot :wink: Thanks!
@halter73 all we need is all the details in a rough draft and any of us can finish it off.
Most helpful comment
@Rick-Anderson assigning the new-and-awesome SignalR label so we can triage these during our regular team triage.