Option to take advantage of `-mute` flag to work around new verification failures about intellij-platform-plugin-verifier-action HOT 3 OPEN

Thanks for the response, @ChrisCarini.

I can see a case for either one here, as each approach has advantages. muteRules would be a more straightforward API, but cliArgs gives that maximum future-facing flexibility.

Regarding cliArgs, since the entry for inputs would just be a string, we might be getting into tricky arg-parsing territory here ("is this space inside quotes or not?"), which may be more trouble than it's worth.

I'll give it a shot. For speed's sake, let's start with mute/muteRules. Sound ok?

from intellij-platform-plugin-verifier-action.

Hi @drewbrokke,

First off, thank you for using this GitHub Action and opening this feature request!

The muteRules option reminds me of failure-levels (implemented in cc63b2c) and is explicit, whereas cliArgs seems like it would be more flexible (e.g. if a similar CLI argument was added to the verifier in the future).

Either solution to the problem seems reasonable to me - is there one you'd recommend over the other? Also, are you interested in having a go at the implementation?

Best,
Chris

from intellij-platform-plugin-verifier-action.

Yeah, I agree with your assessment.

I'll give it a shot. For speed's sake, let's start with mute/muteRules. Sound ok?

SGTM!

from intellij-platform-plugin-verifier-action.