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.

Sign up for GitHub

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

Jump to bottom

tParam rewrites value from previous level #170

Closed
f0rmat1k opened this issue May 3, 2016 · 2 comments · Fixed by #171
Closed

tParam rewrites value from previous level #170

f0rmat1k opened this issue May 3, 2016 · 2 comments · Fixed by #171
Labels
bug

Comments

@f0rmat1k
Copy link
Contributor

f0rmat1k commented May 3, 2016

It was quite unexpectedly that tPram w/o force rewrites values from previous level:

head -> tParam('some', 1);
head-child tParam('some', 2, false); // some === 2;

I think, should write about it in the documentation.
@f0rmat1k f0rmat1k changed the title tParam rewrites value tParam rewrites value from previous level May 3, 2016
@mishanga
Copy link
Member

mishanga commented May 3, 2016

I think we should fix this.

@qfox qfox added the bug label May 4, 2016
@Yeti-or Yeti-or mentioned this issue May 28, 2016
Merged
@mishanga
Copy link
Member

Fixed in 4.1.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix tParam reassignment of parent node value. bem/bh
3 participants
@mishanga @qfox @f0rmat1k