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
Various XSD improvements (NLog.Schema package) #3409
Conversation
3a18ab5
to
8d3f2c7
Compare
@304NotModified Think you should also fix this method to recognize private LoggingRule ParseRuleElement(ILoggingConfigurationElement loggerElement)
{
IEnumerable<LogLevel> enableLevels = null;
int minLevel = 0;
int maxLevel = LogLevel.MaxLevel.Ordinal;
string ruleName = null;
string namePattern = null;
bool enabled = true;
bool final = false;
string writeTargets = null;
foreach (var childProperty in loggerElement.Values)
{
switch (childProperty.Key?.Trim().ToUpperInvariant())
{
case "NAME":
if (loggerElement.MatchesName("logger"))
namePattern = childProperty.Value; // Legacy Style
else
ruleName = childProperty.Value;
break;
case "RULENAME":
ruleName = childProperty.Value; // Legacy Style
break; |
This isn't an issue in the XML now isn't? |
I think we have to update the XSD for NLog 5 and recommend the new approach IMO |
Nope but it would make sense that |
ow this is a mistake then. I'm confused why the names aren't in sync... |
Codecov Report
@@ Coverage Diff @@
## release/4.6.4 #3409 +/- ##
==============================================
+ Coverage 80% 80% +<1%
==============================================
Files 358 358
Lines 28373 28378 +5
Branches 3785 3786 +1
==============================================
+ Hits 22750 22763 +13
+ Misses 4537 4521 -16
- Partials 1086 1094 +8 |
Created #3411 |
8d3f2c7
to
1fcd91d
Compare
fixes #3377
related #2394 and #2891