Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SA1629 should accept more punctuation

See original GitHub issue

Using 1.1.0-beta007 I’m seeing a warning when a <remark> ends with an exclamation point.

Issue Analytics

State:
Created 5 years ago
Reactions:7
Comments:10 (5 by maintainers)

Top GitHub Comments

10reactions

Jerichocommented, Jun 12, 2018

Personally I think any punctuation such as !?. should be permitted.

3reactions

vweijsterscommented, Jun 13, 2018

I’ve marked this as an enhancement because I think there is merit in making the allowed punctuation configurable, with the default being only the period.

Top Results From Across the Web

SA1629 bug #2680 - DotNetAnalyzers/StyleCopAnalyzers

SA1629 should also accept other punctuation characters like '!' or '?' as valid line endings. 👍 4

StyleCop.Analyzers: Disable SA1633 & SA1652

I want to disable both of the following rules: SA1633: The file header is missing or not located at the top of the...

W163 repair manual pdf

0 Specifies if SA1500 will allow the while expression of a do/while loop to be on the same line as the closing brace,...

Jellyfin changelog - Awesome Self Hosted - LibHunt

Web API endpoints no longer accept HTTP Form requests; everything must be application/json . NOTE: Plugins that implement endpoints will also have to...

The LOCAL News - Issue 79 by Island and Surrounds

In order to maintain acceptable editorial standards we reserve the right to edit content and, where necessary, the spelling, punctuation, grammar and ...