Move caution plus reword #13191
Closed
Move caution plus reword #13191
Conversation
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
…viders (HeahDude) This PR was merged into the 3.4 branch. Discussion ---------- [Security] clarified the encoding with memory providers Attempt to fix symfony/symfony#35621. Commits ------- aba29b2 [Security] clarified the encoding with memory providers
This PR was merged into the 3.4 branch. Discussion ---------- Fix wording <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/roadmap for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- e43573d Fix wording
* 3.4: minor. refs symfony#13186 [Security] clarified the encoding with memory providers Fix wording
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.
Follows #13188
@HeahDude, while up merging #13188, I noticed, that the documents are quite different and the usage of the
memoryprovider isn't located in thesecurity.rstfile anymore.For now I removed it completely while merging in
4.4and upper.This PR is an attempt to move it to the right place. I also take the context (using
autoalgo) into account.What do you think?