Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I implemented 3 regular expression related rules:
I combined them, as I was searching for a way how the different regex rules could reuse code to reduce the required plumbing. I investigated the (re)use of MS internal
RegexTree
. Unfortunately, that did not help much. The real showstopper in the end is that theRegexNode
's in MS's regex tree, do not make a distinction betweenAAA
andA{3}
, orA+
andA{1,}
. This makes that most analysis can not performed.The regex helper types I introduced:
RegexTree
Allows to analyze a regex (in relation to its
RegexOptions
).RegexNode
Contains the Regex pattern and Regex options related
SyntaxNode
's. Has factory methods to construct fromnew Regex()
)Regex.*
)[System.ComponentModel.DataAnnotations.RegularExpression]
)The generated regex attribute should also be taken into account. That is on my TODO.
The 3 rules I choose, do not require a (full) parsing of the regular expression itself. That would blown up this PR too much.