elierotenberg/coding-styles

My coding styles.

coding-styles's Issues

Forbid implicit imports

We should add a rule that forbids

import * as foo from './foo';

which is not explicit.

Coding style question about `.bind()`

Feel free to ignore this, just wondering why you consider (...params) => method.apply(this, params); to be better than method.bind(this);?

To me method.bind(this) is much more concise and readable as it more directly describes the intention.

.eslintrc?

Does anyone have a eslintrc file they are willing to share that has these rules? That would be so awesome.

Why tabs are evil in ES6?

I have been using tabs till now for all javascript development. But recently I've seen this ES6 style guide which mentions "Tabs are evil. Don't use them!" at least three times.

I hope there is some rationale behind including this sentence. If there are any scenarios in which using soft tabs instead of hard tabs is superior, a descriptive note (explaining about the reason behind this recommendation) will be helpful. Otherwise, please change the wording, since it makes an impression that using tabs might break something (even some corner-cases).

Thanks!

Immediate invocation of ES6 shorthand generator?

Doesn't work (throws unexpected token):

app.use(*g() {
  this.body = 'hello world';
});

Works:

app.use(function *() {
  this.body = 'hello world';
});

Any insight as to why?

About void 0 & undefined.

Have read your article.

undefined

undefined must not be used, void 0 must be used instead.
// bad
if(x === undefined) {
 ...
}

// good
if(x === void 0) {
...
}

Is it really bad? undefined is a primitive data type, void is an operator, which always returns undefined. Are you serious? Can you describe the sense?

I can see the only sense with defending against fools, who may override undefined. The only sense... But it's also another question... If a fool is coding, then he may do many stupid things...