-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Add xml comments to HubInvocationContext #11683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SMITHED!
Co-Authored-By: Andrew Stanton-Nurse <[email protected]>
/// <summary> | ||
/// Instantiates a new instance of the <see cref="HubInvocationContext"/> class. | ||
/// </summary> | ||
/// <param name="context">Context for the active hub connection and caller.</param> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:Should this be "hub connection" or HubConnection
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it should be HubConnection
as that is the client side type, on the server it's a "connection to a hub" i.e. "hub connection". But I could be convinced either way
public HubInvocationContext(HubCallerContext context, string hubMethodName, object[] hubMethodArguments) | ||
{ | ||
HubMethodName = hubMethodName; | ||
HubMethodArguments = hubMethodArguments; | ||
Context = context; | ||
} | ||
|
||
/// <summary> | ||
/// Gets the context for the active hub connection and caller. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question here
Let the word-smithing begin!