-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[FrameworkBundle] Add validator.expression_language service #39327
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
Conversation
Hey! I like what you have done here. To help keep things organized, we don't allow "Draft" pull requests. Could you please click the "ready for review" button or close this PR and open a new one when you are done? Note that a pull request does not have to be "perfect" or "ready for merge" when you first open it. We just want it to be ready for a first review. Cheers! Carsonbot |
I think this could even be considered as a bugfix. |
Should I rebase on 4.4? |
@fbourigault I don't think so, it looks like a new feature to me. We (or perhaps this is just me really) try to be much more conservative in merging non bugs in older branches. And reading the description/code, it does not looks like a bug to me. |
Thank you @fbourigault. |
This add a
validator.expression_language
service to allow better than in-memory caching of validation expression.This also opens possibilities to extend the expression language available in validation expression through the use of
ExpressionFunctionProviderInterface
and a compiler pass.I tried to do something close as what exists for
security.expression_language
service but I still have some questions.ExpressionLanguage
class?#SymfonyHackday