Skip to content
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

Feature: OR-ed plugins #77

Open
wants to merge 10 commits into
base: next
Choose a base branch
from

Conversation

boudekerk
Copy link
Contributor

@boudekerk boudekerk commented Sep 19, 2023

Fixes #76
Fixes #58 (CheckLog could be OR-ed with CheckJira)

Plugins separated by a pipe, will be OR-ed. This is in addition to, and can be combined with, the existing behaviour where any individually define plugins all need to match.

All defined plugins will be executed, and in the end we evaluate if any such "conditions" have failed.

gnustavo and others added 4 commits May 13, 2023 11:17
When reporting checking errors to the user, the fail_on_faults routine
was using the carp/croak methods, which always shows the filename and
line number where the error occurs, even when the error message ends in
a newline.

We don't need this information because it always shows the same place in
which the routine is invoked.

Thanks @nugged for bringing this to my attention. [0]

Ref0: gnustavo@6795420#r113136608
@boudekerk
Copy link
Contributor Author

I've added another commit which makes things a bit less ugly and allows us to log what was evaluated and how.

@boudekerk
Copy link
Contributor Author

Even though functionally the same, I think doing it this way is a bit nicer.

@gnustavo Could you please share your thoughts?

@boudekerk boudekerk changed the title Feature, OR-ed plugins Feature: OR-ed plugins Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants