Skip to content

Make it easier to enable client-side SignalR logging when using server-side Blazor #5624

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.

Sign up for GitHub

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

Jump to bottom
Closed
danroth27 opened this issue Oct 31, 2018 · 2 comments
Closed

Make it easier to enable client-side SignalR logging when using server-side Blazor #5624

danroth27 opened this issue Oct 31, 2018 · 2 comments
Assignees
@rynowak
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed enhancement This issue represents an ask for new feature or an enhancement to an existing one
Milestone
3.0.0-preview4

Comments

@danroth27
Copy link
Member

We should provide a simple way to enable client-side SignalR logging when using server-side Blazor.
@aspnet-hello aspnet-hello transferred this issue from dotnet/blazor Dec 17, 2018
@aspnet-hello aspnet-hello added this to the Backlog milestone Dec 17, 2018
@aspnet-hello aspnet-hello added area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates enhancement This issue represents an ask for new feature or an enhancement to an existing one area-blazor Includes: Blazor, Razor Components labels Dec 17, 2018
@sven5
Copy link

sven5 commented Jan 21, 2019

@danroth27
Looking forward for this feature. In the meantime, is there any way I can manually enable client-side logging?

Thanks
Sven

@danroth27
Copy link
Member Author

@sven5 There are a few community projects out there that you can take a look at:

@rynowak rynowak mentioned this issue Mar 18, 2019
Closed
8 tasks
rynowak added a commit that referenced this issue Mar 29, 2019
@rynowak
Example of configuring client-side logging
9c6267a 
This commit will eventually fix #6887 and #6887 and #5624

I've done just about the simplest thing so far, I thought I would stop
and get feedback on the general pattern before we move forward.
@rynowak rynowak mentioned this issue Mar 29, 2019
Merged
@rynowak rynowak self-assigned this Mar 29, 2019
@rynowak rynowak modified the milestones: Backlog, 3.0.0-preview4 Mar 29, 2019
rynowak pushed a commit that referenced this issue Mar 29, 2019
Improve initialization and SignalR configuration
65b7977 
Fixes: #6887 and #6887 and #5624

Adds support for calling Blazor.start({...}) and passing in a
configuration object.

For now all you can configure is the SignalR HubConnectionBuilder. This
is a priority right now because we want to make configuring SignalR's
logging accessible.
rynowak pushed a commit that referenced this issue Apr 1, 2019
@rynowak
Improve initialization and SignalR configuration
c6576dd 
Fixes: #6887 and #6887 and #5624

Adds support for calling Blazor.start({...}) and passing in a
configuration object.

For now all you can configure is the SignalR HubConnectionBuilder. This
is a priority right now because we want to make configuring SignalR's
logging accessible.
rynowak pushed a commit that referenced this issue Apr 2, 2019
Improve initialization and SignalR configuration
1423d50 
Fixes: #6887 and #6887 and #5624

Adds support for calling Blazor.start({...}) and passing in a
configuration object.

For now all you can configure is the SignalR HubConnectionBuilder. This
is a priority right now because we want to make configuring SignalR's
logging accessible.
rynowak pushed a commit that referenced this issue Apr 2, 2019
@rynowak
Improve initialization and SignalR configuration
ddb5047 
Fixes: #6887 and #6887 and #5624

Adds support for calling Blazor.start({...}) and passing in a
configuration object.

For now all you can configure is the SignalR HubConnectionBuilder. This
is a priority right now because we want to make configuring SignalR's
logging accessible.
rynowak pushed a commit that referenced this issue Apr 2, 2019
@rynowak
Improve initialization and SignalR configuration
f0ef107 
Fixes: #6887 and #6887 and #5624

Adds support for calling Blazor.start({...}) and passing in a
configuration object.

For now all you can configure is the SignalR HubConnectionBuilder. This
is a priority right now because we want to make configuring SignalR's
logging accessible.
rynowak pushed a commit that referenced this issue Apr 2, 2019
@rynowak
Improve initialization and SignalR configuration
f2e9ef3 
Fixes: #6887 and #6887 and #5624

Adds support for calling Blazor.start({...}) and passing in a
configuration object.

For now all you can configure is the SignalR HubConnectionBuilder. This
is a priority right now because we want to make configuring SignalR's
logging accessible.
@rynowak rynowak added the Done This issue has been fixed label Apr 2, 2019
@rynowak rynowak closed this as completed Apr 2, 2019
@mkArtakMSFT mkArtakMSFT removed area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels May 9, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rynowak rynowak

Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed enhancement This issue represents an ask for new feature or an enhancement to an existing one
Projects
None yet
Milestone
3.0.0-preview4
Development

No branches or pull requests
5 participants
@rynowak @danroth27 @sven5 @mkArtakMSFT @aspnet-hello