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
fix(compiler): throw an error if variable with the same name is already defined. #7209
Conversation
Does this also throw when the variable is added multiple times like
This is sometimes handy and didn't cause issues for me so far. |
@zoechi This change will not influence your case because it checks duplicates on template level, and ngFor creates separate templates. I've checked it locally :) |
@Ne4istb great, thanks for the feedback :) |
I am sorry for the delay in getting back to you. Please add one more tests, which says that the same variables across different templates are OK.
The above is allowed. |
Will do soon |
@tbosch What kind of cleanup should be done? |
The test that @mhevery mentioned... |
Try to rebase, master should be good again. |
@tbosch <div #a><template #a><span>OK</span></template></div> |
…dy defined. (angular#7209) * fix(compiler): throw an error if variable with the same name is already defined. Closes angular#6492 * fix(compiler): Clean up formatting for issue angular#6492 * fix(compiler): throw an error if reference with the same name is already defined. Closes angular#6492
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.