Skip to content

Commit

Permalink
updating messages to become a bit more clear
Browse files Browse the repository at this point in the history
  • Loading branch information
@maryamariyan
maryamariyan committed Jul 28, 2021
1 parent 7c668b7 commit 88ed19a
Show file tree
Hide file tree
Showing 18 changed files with 441 additions and 437 deletions.
30 changes: 15 additions & 15 deletions ...nalyzers/Core/Microsoft.CodeQuality.Analyzers/MicrosoftCodeQualityAnalyzersResources.resx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -172,49 +172,49 @@
<value>Abstract type '{0}' should not have public constructors</value>
</data>
<data name="LoggerMessageDiagnosticNumericsInFormatStringTitle" xml:space="preserve">
<value>Numerics should not be used in logging format string</value>
<value>Named holes should not be numeric values</value>
</data>
<data name="LoggerMessageDiagnosticNumericsInFormatStringMessage" xml:space="preserve">
<value>Numerics should not be used in logging format string</value>
<value>Named holes in the logging message template should not be comprised of only numeric characters</value>
</data>
<data name="LoggerMessageDiagnosticNumericsInFormatStringDescription" xml:space="preserve">
<value>Numerics should not be used in logging format string.</value>
<value>Named holes in the logging message template should not be comprised of only numeric characters.</value>
</data>
<data name="LoggerMessageDiagnosticFormatParameterCountMismatchTitle" xml:space="preserve">
<value>Logging format string parameter count mismatch</value>
<value>Parameter count mismatch</value>
</data>
<data name="LoggerMessageDiagnosticFormatParameterCountMismatchMessage" xml:space="preserve">
<value>Logging format string parameter count mismatch</value>
<value>Number of parameters supplied in the logging message template do not match the number of named holes</value>
</data>
<data name="LoggerMessageDiagnosticFormatParameterCountMismatchDescription" xml:space="preserve">
<value>Logging format string parameter count mismatch.</value>
<value>Number of parameters supplied in the logging message template do not match the number of named holes.</value>
</data>
<data name="LoggerMessageDiagnosticUseCompiledLogMessagesTitle" xml:space="preserve">
<value>Use compiled log messages</value>
<value>Use the LoggerMessage delegates</value>
</data>
<data name="LoggerMessageDiagnosticUseCompiledLogMessagesMessage" xml:space="preserve">
<value>For improved performance, use pre-compiled log messages instead of calling '{0}' with a string message</value>
<value>For improved performance, use the LoggerMessage delegates instead of calling '{0}'</value>
</data>
<data name="LoggerMessageDiagnosticUseCompiledLogMessagesDescription" xml:space="preserve">
<value>For improved performance, use pre-compiled log messages.</value>
<value>For improved performance, use the LoggerMessage delegates.</value>
</data>
<data name="LoggerMessageDiagnosticConcatenationInFormatStringTitle" xml:space="preserve">
<value>Logging format string should not be dynamically generated</value>
<value>Template should be a static expression</value>
</data>
<data name="LoggerMessageDiagnosticConcatenationInFormatStringMessage" xml:space="preserve">
<value>Logging format string should not be dynamically generated</value>
<value>The logging message template should not vary between calls to '{0}'</value>
</data>
<data name="LoggerMessageDiagnosticConcatenationInFormatStringDescription" xml:space="preserve">
<value>Logging format string should not be dynamically generated.</value>
<value>The logging message template should not vary between calls.</value>
</data>
<data name="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensTitle" xml:space="preserve">
<value>Use PascalCase for log message tokens</value>
<value>Use PascalCase for named holes</value>
</data>
<data name="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensMessage" xml:space="preserve">
<value>For consistency with logs emitted from other components, use 'PascalCase' for log message tokens</value>
<value>Use PascalCase for named holes in the logging message template</value>
</data>
<data name="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensDescription" xml:space="preserve">
<value>For consistency with logs emitted from other components, use 'PascalCase' for log message tokens.</value>
<value>Use PascalCase for named holes in the logging message template.</value>
</data>
<data name="MarkAssembliesWithClsCompliantTitle" xml:space="preserve">
<value>Mark assemblies with CLSCompliant</value>
Expand Down
60 changes: 30 additions & 30 deletions ...rs/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.cs.xlf
View file
Original file line number Diff line number Diff line change
Expand Up @@ -243,78 +243,78 @@
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticConcatenationInFormatStringDescription">
<source>Logging format string should not be dynamically generated.</source>
<target state="new">Logging format string should not be dynamically generated.</target>
<source>The logging message template should not vary between calls.</source>
<target state="new">The logging message template should not vary between calls.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticConcatenationInFormatStringMessage">
<source>Logging format string should not be dynamically generated</source>
<target state="new">Logging format string should not be dynamically generated</target>
<source>The logging message template should not vary between calls to '{0}'</source>
<target state="new">The logging message template should not vary between calls to '{0}'</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticConcatenationInFormatStringTitle">
<source>Logging format string should not be dynamically generated</source>
<target state="new">Logging format string should not be dynamically generated</target>
<source>Template should be a static expression</source>
<target state="new">Template should be a static expression</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticFormatParameterCountMismatchDescription">
<source>Logging format string parameter count mismatch.</source>
<target state="new">Logging format string parameter count mismatch.</target>
<source>Number of parameters supplied in the logging message template do not match the number of named holes.</source>
<target state="new">Number of parameters supplied in the logging message template do not match the number of named holes.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticFormatParameterCountMismatchMessage">
<source>Logging format string parameter count mismatch</source>
<target state="new">Logging format string parameter count mismatch</target>
<source>Number of parameters supplied in the logging message template do not match the number of named holes</source>
<target state="new">Number of parameters supplied in the logging message template do not match the number of named holes</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticFormatParameterCountMismatchTitle">
<source>Logging format string parameter count mismatch</source>
<target state="new">Logging format string parameter count mismatch</target>
<source>Parameter count mismatch</source>
<target state="new">Parameter count mismatch</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticNumericsInFormatStringDescription">
<source>Numerics should not be used in logging format string.</source>
<target state="new">Numerics should not be used in logging format string.</target>
<source>Named holes in the logging message template should not be comprised of only numeric characters.</source>
<target state="new">Named holes in the logging message template should not be comprised of only numeric characters.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticNumericsInFormatStringMessage">
<source>Numerics should not be used in logging format string</source>
<target state="new">Numerics should not be used in logging format string</target>
<source>Named holes in the logging message template should not be comprised of only numeric characters</source>
<target state="new">Named holes in the logging message template should not be comprised of only numeric characters</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticNumericsInFormatStringTitle">
<source>Numerics should not be used in logging format string</source>
<target state="new">Numerics should not be used in logging format string</target>
<source>Named holes should not be numeric values</source>
<target state="new">Named holes should not be numeric values</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUseCompiledLogMessagesDescription">
<source>For improved performance, use pre-compiled log messages.</source>
<target state="new">For improved performance, use pre-compiled log messages.</target>
<source>For improved performance, use the LoggerMessage delegates.</source>
<target state="new">For improved performance, use the LoggerMessage delegates.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUseCompiledLogMessagesMessage">
<source>For improved performance, use pre-compiled log messages instead of calling '{0}' with a string message</source>
<target state="new">For improved performance, use pre-compiled log messages instead of calling '{0}' with a string message</target>
<source>For improved performance, use the LoggerMessage delegates instead of calling '{0}'</source>
<target state="new">For improved performance, use the LoggerMessage delegates instead of calling '{0}'</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUseCompiledLogMessagesTitle">
<source>Use compiled log messages</source>
<target state="new">Use compiled log messages</target>
<source>Use the LoggerMessage delegates</source>
<target state="new">Use the LoggerMessage delegates</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensDescription">
<source>For consistency with logs emitted from other components, use 'PascalCase' for log message tokens.</source>
<target state="new">For consistency with logs emitted from other components, use 'PascalCase' for log message tokens.</target>
<source>Use PascalCase for named holes in the logging message template.</source>
<target state="new">Use PascalCase for named holes in the logging message template.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensMessage">
<source>For consistency with logs emitted from other components, use 'PascalCase' for log message tokens</source>
<target state="new">For consistency with logs emitted from other components, use 'PascalCase' for log message tokens</target>
<source>Use PascalCase for named holes in the logging message template</source>
<target state="new">Use PascalCase for named holes in the logging message template</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensTitle">
<source>Use PascalCase for log message tokens</source>
<target state="new">Use PascalCase for log message tokens</target>
<source>Use PascalCase for named holes</source>
<target state="new">Use PascalCase for named holes</target>
<note />
</trans-unit>
<trans-unit id="MarkAttributesWithAttributeUsageCodeFix">
Expand Down
60 changes: 30 additions & 30 deletions ...rs/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.de.xlf
View file
Original file line number Diff line number Diff line change
Expand Up @@ -243,78 +243,78 @@
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticConcatenationInFormatStringDescription">
<source>Logging format string should not be dynamically generated.</source>
<target state="new">Logging format string should not be dynamically generated.</target>
<source>The logging message template should not vary between calls.</source>
<target state="new">The logging message template should not vary between calls.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticConcatenationInFormatStringMessage">
<source>Logging format string should not be dynamically generated</source>
<target state="new">Logging format string should not be dynamically generated</target>
<source>The logging message template should not vary between calls to '{0}'</source>
<target state="new">The logging message template should not vary between calls to '{0}'</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticConcatenationInFormatStringTitle">
<source>Logging format string should not be dynamically generated</source>
<target state="new">Logging format string should not be dynamically generated</target>
<source>Template should be a static expression</source>
<target state="new">Template should be a static expression</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticFormatParameterCountMismatchDescription">
<source>Logging format string parameter count mismatch.</source>
<target state="new">Logging format string parameter count mismatch.</target>
<source>Number of parameters supplied in the logging message template do not match the number of named holes.</source>
<target state="new">Number of parameters supplied in the logging message template do not match the number of named holes.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticFormatParameterCountMismatchMessage">
<source>Logging format string parameter count mismatch</source>
<target state="new">Logging format string parameter count mismatch</target>
<source>Number of parameters supplied in the logging message template do not match the number of named holes</source>
<target state="new">Number of parameters supplied in the logging message template do not match the number of named holes</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticFormatParameterCountMismatchTitle">
<source>Logging format string parameter count mismatch</source>
<target state="new">Logging format string parameter count mismatch</target>
<source>Parameter count mismatch</source>
<target state="new">Parameter count mismatch</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticNumericsInFormatStringDescription">
<source>Numerics should not be used in logging format string.</source>
<target state="new">Numerics should not be used in logging format string.</target>
<source>Named holes in the logging message template should not be comprised of only numeric characters.</source>
<target state="new">Named holes in the logging message template should not be comprised of only numeric characters.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticNumericsInFormatStringMessage">
<source>Numerics should not be used in logging format string</source>
<target state="new">Numerics should not be used in logging format string</target>
<source>Named holes in the logging message template should not be comprised of only numeric characters</source>
<target state="new">Named holes in the logging message template should not be comprised of only numeric characters</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticNumericsInFormatStringTitle">
<source>Numerics should not be used in logging format string</source>
<target state="new">Numerics should not be used in logging format string</target>
<source>Named holes should not be numeric values</source>
<target state="new">Named holes should not be numeric values</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUseCompiledLogMessagesDescription">
<source>For improved performance, use pre-compiled log messages.</source>
<target state="new">For improved performance, use pre-compiled log messages.</target>
<source>For improved performance, use the LoggerMessage delegates.</source>
<target state="new">For improved performance, use the LoggerMessage delegates.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUseCompiledLogMessagesMessage">
<source>For improved performance, use pre-compiled log messages instead of calling '{0}' with a string message</source>
<target state="new">For improved performance, use pre-compiled log messages instead of calling '{0}' with a string message</target>
<source>For improved performance, use the LoggerMessage delegates instead of calling '{0}'</source>
<target state="new">For improved performance, use the LoggerMessage delegates instead of calling '{0}'</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUseCompiledLogMessagesTitle">
<source>Use compiled log messages</source>
<target state="new">Use compiled log messages</target>
<source>Use the LoggerMessage delegates</source>
<target state="new">Use the LoggerMessage delegates</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensDescription">
<source>For consistency with logs emitted from other components, use 'PascalCase' for log message tokens.</source>
<target state="new">For consistency with logs emitted from other components, use 'PascalCase' for log message tokens.</target>
<source>Use PascalCase for named holes in the logging message template.</source>
<target state="new">Use PascalCase for named holes in the logging message template.</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensMessage">
<source>For consistency with logs emitted from other components, use 'PascalCase' for log message tokens</source>
<target state="new">For consistency with logs emitted from other components, use 'PascalCase' for log message tokens</target>
<source>Use PascalCase for named holes in the logging message template</source>
<target state="new">Use PascalCase for named holes in the logging message template</target>
<note />
</trans-unit>
<trans-unit id="LoggerMessageDiagnosticUsePascalCasedLogMessageTokensTitle">
<source>Use PascalCase for log message tokens</source>
<target state="new">Use PascalCase for log message tokens</target>
<source>Use PascalCase for named holes</source>
<target state="new">Use PascalCase for named holes</target>
<note />
</trans-unit>
<trans-unit id="MarkAttributesWithAttributeUsageCodeFix">
Expand Down
Loading

0 comments on commit 88ed19a

Please sign in to comment.