File RegEx rule #339
File RegEx rule #339
Conversation
This rule template can be used to create rules which will be triggered when a file matches a given regular expression. Additional a Ant-style matching pattern for the path can be defined.
|
This is really a general search of a regex pattern in a file. The search for the include is only one example. So I would keep the name file regex. I'm thinking about a second one which is searching only in a line: LineRegularExpressionCheck. |
|
The intension was to have two general ways to create rules: xpath and regex. |
|
Oh I see. I missed this point. |
|
Off topic: do you have more features in the queue? I'd like to call a feature freeze in the next days... |
|
No. The only two missing points for me were the possibility to create own rules with xpath and regex. Other open point for me is to try out new unit test behavior. Not sure if current implementation fits our boost test usage. Here I'm waiting for your description to start testing. Looking to bugs the important ones seems to be #226 and #49. Especially #49 becomes more and more important but I have still no idea how to solve it. |
This rule template can be used to create rules which will be triggered when a file matches a given regular expression. Additional a Ant-style matching pattern for the path can be defined.
Also a solution for #179.