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

#519 Update template #520

Closed
wants to merge 1 commit into from
Closed

#519 Update template #520

wants to merge 1 commit into from

Conversation

ilyar
Copy link
Contributor

@ilyar ilyar commented May 8, 2014

No description provided.

@ilyar ilyar changed the title Update template #519 Update template May 8, 2014
@ilyar ilyar changed the title Update template #519 Update template May 8, 2014
@@ -62,6 +62,7 @@ exports.techMixin = {

vars.ElemName && tmpl.push('.elem(\'{{bemElemName}}\')');
vars.ModVal && tmpl.push('.' + (vars.ElemName ? 'elemMod' : 'mod') + '(\'{{bemModName}}\', \'{{bemModVal}}\')');
tmpl.push('()');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've got 2 arguments to left it as is:

  1. If there's no template for the block it's better to remove it. So when compilation fails it's like a kind of linting saying "there's something wrong with your code, go and fix".
  2. there are a lot of templates with just one custom mode and it's convenient to write them in "dot-notation": block('bla').js()(true); or block('bla').content()(/* ... */); so having parenthesis will disturb.

@ilyar ilyar closed this Jul 15, 2014
@ilyar ilyar deleted the issues/519@v2 branch July 15, 2014 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants