Merge release 2.13.0 into 3.0.x #161
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…ole` is available Fixes #149 Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
To avoid having PCRE compilation error regarding `number too big`, we have to limit the maximum key length of the decorator. This will allow us to keep the performance benefits of `preg_match` while still allowing more than the initial 64 characters limit. Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
boesing
force-pushed
the
2.13.x-merge-up-into-3.0.x_rFExZKZd
branch
from
566948e
to
4ddd065
Compare
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes for 2.13.0
Feature release (minor)
Changed
PatternFactoryno longer suggests thePatternPluginManageras an alternative.Deprecated
PatternPluginManageras with v3.0.0, cache pattern do require strict dependency injection. Since most of the cache pattern depend on a storage implementation, which are not longer known by this component as of v3, a dynamic factory for the cache pattern won't be suitable anymore.PatternCacheFactoryandStoragePatternCacheFactorywhich were introduced in v2.12.0 to provide forward compatibility for the newStorageCapableInterfaceimplementing patterns.2.13.0
Enhancement
PatternPluginManagerand related factories introduced in 2.12.x for BC compatibility thanks to @boesing