(feat):App extras exceptions

[dobri1408]

In situations where we do not want the appExtras rule to apply universally to all routes matched by a certain rule, the addition of an exclude property could be beneficial. This property would provide a way to specify exceptions to the rule. For instance:
{ match: '*', exclude: '/**/diff', component: RemoveSchema, }
To address this scenario, where the goal is to apply a rule to all pages except for the "history diff" page, incorporating an exclude property into the rule configuration is an effective solution.

[netlify]

✅ Deploy Preview for plone-components canceled.

Name	Link
🔨 Latest commit	896f036
🔍 Latest deploy log	https://app.netlify.com/sites/plone-components/deploys/65be8051a663d60008f22146

[netlify]

✅ Deploy Preview for volto ready!

Name	Link
🔨 Latest commit	896f036
🔍 Latest deploy log	https://app.netlify.com/sites/volto/deploys/65be8051807a8b0007528641
😎 Deploy Preview	https://deploy-preview-5621--volto.netlify.app/recipes/appextras.html
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dobri1408]

Also, if this is merged, can we backport it to version 16.x?

[stevepiercy]

This needs narrative documentation. See https://6.docs.plone.org/volto/recipes/appextras.html.

I would like to see an exclude code example, modeled on the default code example.

Additionally, we need to include a placeholder for this admonition, especially if it gets backported.

```{versionchanged}17.x.x and 16.x.x
Added the `exclude` property.
```

Side note, that page has some syntax and grammar issues that could be addressed at the same time.

[ichim-david]

https://github.com/plone/volto/pull/5621/files#diff-76050b5a1b7f3811d861cba8076fb99be2f8162e0649b91432f7793702071078R3

The matching rule isn't correct, look at the test output, now every test returns null which means that your condition always renders true.

[dobri1408]

@ichim-david, you're right, the default value was incorrect.

[ichim-david]

@dobri1408 you need to add a test for this feature

[ichim-david]

@dobri1408 do not put your code that you want to test inside the beforeAll call which is called for each test.
Write a new test that passes the exclude and see how it behaves leaving the other tests as they were before you worked on this feature.

[ichim-david]

This needs narrative documentation. See https://6.docs.plone.org/volto/recipes/appextras.html.

I would like to see an exclude code example, modeled on the default code example.

Additionally, we need to include a placeholder for this admonition, especially if it gets backported.

```{versionchanged}17.x.x and 16.x.x
Added the `exclude` property.

Side note, that page has some syntax and grammar issues that could be addressed at the same time.

@dobri1408 don't forget to also do this step that @stevepiercy mentioned that you need todo

[tiberiuichim]

I think I would prefer a setting called ignore, rather then exclude.

[sneridagh]

out of curiosity, the react-router-dom matchPath support regex, right? Can't we build a regex that does this? (I am not a regex nerd, but still...)

[dobri1408]

Hi @sneridagh! This was my first thought, but unfortunately no, it doesn't support regex so we have to introduce this new property.

[sneridagh]

@dobri1408 please perform the suggestions from @ichim-david and @tiberiuichim I think they are valuable.

[stevepiercy]

These suggestions might need more revision, and should be reviewed by someone who can make sure the rewording I suggested aligns with the code functionality. Thank you!

[stevepiercy]

One more change, after checking the preview on Netlify.

[stevepiercy]

Thank you!

[ichim-david]

@sneridagh this is ready to merge for some time and everyone gave their approval, can we merge this or do you want to merge something else before?