Skip to content

[Security] register custom providers on ExpressionLanguage directly #26802

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 4, 2018

Conversation

dmaicher
Copy link
Contributor

@dmaicher dmaicher commented Apr 4, 2018

Q A
Branch? 3.4
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets -
License MIT
Doc PR -

This is a fix on 3.4 related to #26660.

See the comment from @stof here: #26660 (comment)

@fabpot
Copy link
Member

fabpot commented Apr 4, 2018

Thank you @dmaicher.

@fabpot fabpot merged commit 3a55a86 into symfony:3.4 Apr 4, 2018
fabpot added a commit that referenced this pull request Apr 4, 2018
… directly (dmaicher)

This PR was merged into the 3.4 branch.

Discussion
----------

[Security] register custom providers on ExpressionLanguage directly

| Q             | A
| ------------- | ---
| Branch?       | 3.4
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | -

This is a fix on 3.4 related to #26660.

See the comment from @stof here: #26660 (comment)

- fixes a bug where custom providers would not be registered when retrieving the `security.expression_language` instance without the `ExpressionVoter` being instantiated.
- avoids deprecations on 3.4 when using the 4.1 patch in #26660

Commits
-------

3a55a86 [Security] register custom providers on ExpressionLanguage directly
This was referenced Apr 6, 2018
@dmaicher dmaicher deleted the fix-23208-3.4 branch November 30, 2018 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants