Repository navigation
#73 - RequestTransformer: private again - #74
Merged
Merged
Conversation
…public by mistake in 3.3). Update UPGRADE.md and tests. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
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.
Description
Fixes #73.
config/services/transformer.yaml:public: false, nocontainer.privatetag:RequestTransformerwas private in 3.2, 3.3 made it public by mistake (and deprecated this new access at once).UPGRADE.md(3.3): only the task is concerned by the deprecated direct access.CleverAgeSoapProcessExtensionTestupdated.Requirements
Breaking changes
Only code fetching
RequestTransformerdirectly from the service container since 3.3 (with a deprecation) is concerned; it was not possible in 3.2.🤖 Generated with Claude Code