-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Figure out a way to allow configuring SignalR settings on the client. #6887
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
Comments
It’s coming from SignalR @BrennanConroy |
How to change the log level? |
I'm trying to update my components libraries to the new RC 3.0 preview. When I start the app it does not show. The only thing that I get are this messages in the console
I really don't see what is wrong, basically I have updated all my project files according to the default Razor Components app. Can you guys point what can I do? |
@stsrki |
I'm just starting it without debugging(CTRL+F5). There is nothing unusual in the output window. I just saw this in the blog post
Could be the reason why it's not working as I have some js and css files in the component library projects. |
@BrennanConroy can you please share details regarding how to control this? Also, we'd like to disable the default to not have these logs by default. |
https://docs.microsoft.com/en-us/aspnet/core/signalr/configuration?view=aspnetcore-2.2&tabs=dotnet#configure-logging |
In Razor Components, the client connection is established here:https://github.com/aspnet/AspNetCore/blob/33839dc66a9e6eb730e22e7b6d9d381bcf7b4779/src/Components/Browser.JS/src/Boot.Server.ts#L44-L49 |
The current SignalR connection on the client is set up to print info logs, but this isn't required in the general case. However it would be useful to retain the ability to configure the log level among other things, in the event the user's attempting to debug connection issues on the client.
Original issue report
When running a Razor Components app you see the following log output in the browser console.
We should investigate why we are logging Information level messages by default and how a user would change the log level.
The text was updated successfully, but these errors were encountered: