Where are the "Context (any)" and "Context (all)" conditions

Would love to see this moving forward.... can't provide code but will happily test and provide feedback

This probably requires some changes in the main context system, as this patch currently creates an infinite loop.

Basically, on evaluate, activeContexts is fired, which runs evaluate for all conditions on all contexts, and thus will fire the evaluate on the Context (any) condition, which will then fire activeContexts, etc.

Based on the description, some technique should be employed that would only run the Context (all) check after all the other conditions have fired; but I don't think there is mechanism for that currently. Another way would be to duplicate the context triggering logic within the plugin, but that would be hard to maintain.

A first stab at making this work. Similarly to the D7 version, we'll have to evaluate the contexts directly as they are being referenced in the `context_any` plugin.

Fixed some code style issues

Also include context (all) condition plugin this time.

Fixed an issue with duplicate plugin id

Included cache context support.

Fixed an issue around negated contexts. These conditions probably need some testing

I tested with different conditions and reactions and it look like it works

Hi guys, I was unable to apply the patch. You may have to update

Patch needs re-roll

I re-rolled the patch, but the asterisk (*) is not working (fatal error is thrown because null is returned), so I'm currently debugging why as it seems this was also not working in the D7 version.

I created a new fork as it's more manageable and pushed the re-rolled patch with the asterisks/wildcard handling. Needs additional testing.
If necessary I can also upload the .patch file. Setting to needs review.

Hi @DeaOm,
I was testing it and I found a bug.
Steps to reproduce:
1) Create a context that will add a block if the current page is the front page.
2) Create a second context with "Context (any)" condition, add the context created in step 1 and add a page title reaction.
3) Save it and see the error below:

Warning: Undefined array key "" in Drupal\context\ContextManager->getContext() (line 169 of modules/contrib/context/src/ContextManager.php).
Warning: foreach() argument must be of type array|object, null given in Drupal\context\Plugin\Condition\ContextAny->evaluate() (line 164 of modules/contrib/context/src/Plugin/Condition/ContextAny.php).

Hi @paulocs, I could reproduce your bug. I pushed changes for that bug/issue to the MR, so setting status to needs review.

I found another error when adding a context id that does not exist.
The site totally crashes if I write a wrong context id and I'm not even able to edit the context and fix it.

I tested it with Context (any).

Added the updated code to context any and all condition. Not sure how to actually handle the wrong name, as the code will work, but the user will have no idea that the entered context name is wrong. Here is kinda assumed you know what you are doing, so the complete crash of the page of course is not correct, but maybe some kind of a warning could be displayed? For when user mistypes or something. Setting it to needs review and we'll see from there.

I tested and the re-rrol works. But when I adding a context that not exist, it's save normally. I tested in Drupal 7 to see how this case works there and I see that when adding a context that not exists, it's save normally too.

Thanks!
It looks good to me as well.
I'll commit and add it to the next release.