Paul Biron

> I did at first think about this but then plugins that sell like me would require requirements to be filled such: > > * An active licence or >...

That's what I thought you meant. And that's why in the sample code I added the comment: > // note: in a real implementation, the 2nd param to the filter...

Yeah, `uninterpolated string` is probably too "technical" :-) But `plain string` is not clear either. Let me think about it (and read the PHP manual to see how it describes...

How about `an integer or string without embedded variables`?

> Also, it's not just about _embedded_ or interpolated variables. The rule also applies to concatenated keys or keys created via a calculation: `$a[ 'a' . $text ]` or `$a[...

We don't **need** it, but it's certainly a "nice to have". At least 2 of the sample blocks that were mentioned in @paaljoachim 's (now closed) ticket are dynamic blocks...

Something which should be discussed before jumping in with a proposed patch is: what should happen if the plugins specified in `--skip-plugins-except=` are **not** currently active? A couple of options...

> Because global parameters conflict with local parameters... Can you elaborate on this. I think you're saying that there is a _possibility_ that `--skip-plugins-except=` could conflict with the `--=` parameter...

> @pbiron Someone could have developed a custom command with a `--skip-plugins-except` parameter. If we now add such a global parameter in WP-CLI, we would break their command. Hope that...

> It could be worth exploring other ways of achieving this same goal, though. Just spitballing here, but maybe we could introduce new syntax for the existing `--skip-plugins` param, such...