-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ignore/forcefail/forcepass as regexes #75
Comments
That's a great idea. Concerning implementation, I don't think performance would suffer much since the amount of data to match is pretty short, as is would the regular expression. |
It is a good idea, indeed. Let's add it to our backlog. |
Hi, I wrote some (most likely dumb) code: Draft PR #80 .
Now that becomes a regex leads to also remove rules like Thoughts about it? Could it be better to add other lists (something like
|
Cool, thanks for your contribution! I think we can simplify this, as we moved test inclusion/exclusion to regexp's. It will make things easier for everyone if we use the same pattern. That should simplify things a lot. And we only need to document it. |
Hi there, I implemented it in a bit better way (at least avoiding regex generation inside loops 😅) and added a bit of documentation about it. I removed the draft status from the PR, please provide me any advice about better implementing it! |
Hello,
I was wondering if it could be helpful to provide to the
testoverride
lists (ignore
,forcefail
andforcepass
) a regex syntax like the-i
/-e
commands. The use case comes from a willingness to exclude all the tests of some specific rules (or even a specific file?) and, currently, the only way I see is listing individually all the tests in a quite verbose way.Before:
After:
My concern is about the implementation: the check would become not just looking for the a value inside the map (e.g. ignore), but iterating over a list of regex looking for a match. Do you think it's worth the overhead?
Thanks for the feedbacks!
The text was updated successfully, but these errors were encountered: