Implement true "regex" support.

[tfuda]

Currently the two options -regex.for.selecting.source.classes.for.code.coverage.computation and -regex.for.selecting.test.classes.to.execute can be used to specify a comma separated list of patterns for selecting classes. The patterns support simple wildcard substitution and are converted into SOQL LIKE clauses. For example the pattern Test would be converted into WHERE Name LIKE '%Test%'. This is technically not true regex pattern matching. In order to support true regex pattern matching, I think you would have to query all Apex classes in the specified namespace and then iterate through the result set, and then use the Java Pattern and/or Matcher classes to see if the class names match the specified regex.

[pmedapuram]

Here (refer to the comment at the bottom) is the reference to the use case provided by @tfuda .
Thank you @tfuda

[adarsh-ramakrishna-sfdc]

Implementing the 'true' regex support would require finding a way to honor the regex patterns in the soql queries along with using the matching logic as mentioned by @tfuda . This will take more time to implement and unfortunately we don't have the bandwidth for this. However we would welcome the community to help and contribute to this enhancement request.

[aabrego]

I see some scenarios where the true REGEX support can become very useful. I will start working on this one step at a time ...

[vamshi-sfdc]

@aabrego have you had a chance to look into this? Please let us know

[KThompso]

Has there been any movement on this issue? I have a use for this feature and would be willing to provide support if it's being worked on -- or implement it if it's not.

[aabrego]

No progress on this one and no plans on working on it for now due to other prorities. Volunteers are welcome.Thanks!

…

On Mon, Oct 22, 2018, 8:36 PM KThompso ***@***.***> wrote: Has there been any movement on this issue? I have a use for this feature and would be willing to provide support if it's being worked on -- or implement it if it's not. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAiaSH0RRsBWW7nuuiiWB9FgM2-AiChCks5uno60gaJpZM4HI40r> .