-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Subexpression parameters issue #758
Comments
see #743 |
Closing as dupe of #743. Please let me know if you have issues with the latest 2.0.0 alpha. |
The JSFiddle example is built on version "2.0.0-alpha.2" so it has fix of issue #743 included. |
The issue was opened for latest version. As @evensoul said it should have been fixed in previous updates. |
It looks like we have issues with multiple helpers that use nested reference lookups. The tests for this is #768 |
Hi everyone!
I have detected a bug when using subexpressions and values from objects in context.
For example:
→ We have helper with two nested subexpressions.
→ Each subexpression uses some value that is attached to context.
→ Bug is triggered if both of those values from context are part of some object (also contained in context).
→For instance:
{{helper_1 a=(helper_2 item.X) b=(helper_2 item.Y) }}
As explained, using item.X and item.Y triggers bug. Same happens if values are on different objects in context: item_1.X, item_2.Y.
Bug result: instead of value for X or Y we get whole referenced object from context (whole item_1 or item_2).
I have created few simple example's on JSFiddle for better understanding and demonstration: JSFiddle
Best regards,
Tomislav
The text was updated successfully, but these errors were encountered: