-
Notifications
You must be signed in to change notification settings - Fork 817
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
"include" broken by v2.5.4 with two-arg invocation #221
Comments
Here's the offending commit: 3a534a9 |
I think this was on purpose, context mixed with options is a bad practice, and highly discouraged. |
The README says: It goes on to say that it's not recommended, but I think it's still supported. |
This is still supported in principle, but securing it may mean in practice we have to remove some specific options. Having said that, this particular case looks fixable. If we find other practical problems with these security fixes, we'll start documenting unsupported options. Thanks for your patience with this. |
Thanks! |
The latest release v2.5.4 throws an error when using "include" if "render" was called with two arguments instead of three (context mixed with options).
The text was updated successfully, but these errors were encountered: