-
Notifications
You must be signed in to change notification settings - Fork 222
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
Merge 0.13 #698
Merge 0.13 #698
Conversation
Changes setup of expression language functions to fix issue overblog#588
cherry-pick commits from original overblog#675 fix proposed for 0.13
In the PR #682 I introduces the 2 things here have to be done:
Take into account, that |
done @murtukov ! |
It wasn't really necessary to use ${TypeGenerator::GLOBAL_VARS} = new GlobalVariables(['container' => $this->getDIContainerMock(['toto' => $object])]);
$this->expressionLanguage->evaluate($name.'("toto")', [TypeGenerator::GLOBAL_VARS => ${TypeGenerator::GLOBAL_VARS}]) because you explicitely pass the variable inside the $vars = new GlobalVariables(['container' => $this->getDIContainerMock(['toto' => $object])]);
$this->expressionLanguage->evaluate($name.'("toto")', [TypeGenerator::GLOBAL_VARS => $vars]) The variable name only matters when you use the built-in ${Generator::GLOBAL_VARS} = new GlobalVariables(['security' => new Security($this->createMock(CoreSecurity::class))]);
$this->assertNull(eval($this->getCompileCode())); |
@mcg-web LGTM |
No description provided.