Skip to content
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

Closed
ghost opened this issue Mar 6, 2014 · 4 comments
Closed

Subexpression parameters issue #758

ghost opened this issue Mar 6, 2014 · 4 comments
Labels

Comments

@ghost
Copy link

ghost commented Mar 6, 2014

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

@akileez
Copy link

akileez commented Mar 6, 2014

see #743

@kpdecker
Copy link
Collaborator

Closing as dupe of #743. Please let me know if you have issues with the latest 2.0.0 alpha.

@MarkoZabcic
Copy link
Contributor

The JSFiddle example is built on version "2.0.0-alpha.2" so it has fix of issue #743 included.

@ghost
Copy link
Author

ghost commented Mar 11, 2014

The issue was opened for latest version. As @evensoul said it should have been fixed in previous updates.

@kpdecker kpdecker reopened this May 20, 2014
@kpdecker
Copy link
Collaborator

It looks like we have issues with multiple helpers that use nested reference lookups. The tests for this is #768

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants