-
Notifications
You must be signed in to change notification settings - Fork 165
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
Fix IHttpContextAccessor warning #180
Conversation
Codecov Report
@@ Coverage Diff @@
## master #180 +/- ##
=======================================
Coverage 58.18% 58.18%
=======================================
Files 29 29
Lines 385 385
Branches 93 93
=======================================
Hits 224 224
Misses 125 125
Partials 36 36
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #180 +/- ##
==========================================
- Coverage 58.18% 57.66% -0.52%
==========================================
Files 29 29
Lines 385 385
Branches 93 93
==========================================
- Hits 224 222 -2
Misses 125 125
- Partials 36 38 +2
Continue to review full report at Codecov.
|
@304NotModified Could be nice if AspNetLayoutRendererBase.Initialize() generated a warning, when HttpContextAccessor is null (And not a debug message for every property-access). As the initial proposal suggested #133 (but changed after some refactoring). |
That was the case and we got multiple tickets for the warning. So now debug and only on usage. |
Did you notice comments like these:
Which actually means the logging is not working, because it has been initialized wrong. Maybe the NLog Example should be fixed to perform proper initialization so the layout-renderer works. But anyway just curious, why it has been removed, besides noise from people finding NLog hard to use in ASP.NET (Maybe fix the issue with it being hard to use) |
The new way (working on it), is less difficult to setup :) |
Can't wait on the new way to be released. Please let us know in this trail when released! |
Yes I will! Hopefully this weekend! |
fixes #157