Validate shortcode controllername service configurations (Case 173693)

2.6.0

Validate shortcode controllername service configurations (Case 173693…

Allow never versions of `psr/log` to be used (#39)

What's Changed

• Allow never versions of psr/log to be used by @mpdude in #39

Full Changelog: 2.5.0...2.5.1

Update requirements, fix missing return type hints

What's Changed

• Aktualisiere PHP-CS-Fixer auf v3.62.0 by @mpdude in #36
• Nutze Docker-Image von friendsofphp/php-cs-fixer by @mpdude in #37
• Update test matrix and dependencies to use supported Symfony versions only by @mpdude in #38

Full Changelog: 2.4.0...2.5.0

Compatibility with Symfony 7

2.4.0

Allow Symfony 7 packages (Case 170245) (#33)

Add a form so shortcodes can be tried out in the "guide" (#31)

This adds a textarea to the example pages shown in the "shortcode
guide", so that users can modify the example code given and preview the
results.

Allow symfony 6 packages (#29)

2.2.0

Allow symfony 6 packages (#29)

Fixes a Symfony deprecation notice (#25)

Add a return type hint (#25)

... to avoid a Symfony DebugClassLoader deprecation notice.

Adds semantic bundle configuration and test helper classes

This release brings a new, semantic bundle configuration that makes shortcode definitions more concise (#21).

In addition to that, we have added a few helper classes and some documentation in the README that explains how you could test your shortcode handler implementations and the configuration/usage of this bundle (#23).

Through these two PRs, the README file has undergone a major overhaul, so you might want to re-read it to familiarize yourself with the new features.

Catch all errors thrown when generating shortcode replacements

Catch all errors thrown when generating shortcode replacements (#17)

When a controller that is used to generate shortcode replacements throws an Exception, this exeception will currently fall-through.

I think this kind of errors should be contained, and we should try to display the shortcode as unchanged as possible, as if we had not attempted to resolve it in the first place (of course, logging the problem).

Co-authored-by: Fabian Schmick <[email protected]>

Avoid passing the current request into controllers resolving shortcodes

See #15 – this never worked for ESI-based shortcodes, at least not with Symfony ^4.0.

For inline-based shortcodes you need to review your substitution-generating controllers and check whether they depend on the request Request attribute.

Additionally, the default logging level and channel have been changed, see #5.