feat(symfony): Deprecate the $exceptionOnNoToken
parameter in ResourceAccessChecker::__construct()
#4900
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.
Just syncing with symfony/security: symfony/symfony#41965.
This argument is useless with the not-so-new authenticator system, and it must be
false
everywhere in Symfony 6.The plan is to do the same in 3.0: deprecate the parameter entirely and throw if it's passed as
true
, then remove it in 4.0.The impact of this deprecation is likely to be small since very few or nobody should be extending this class anyway.