Kevin Suttle

In Webpack, you can do this with CSS Loader, ``` js css-loader?localIdentName=[path][name]---[local]--- ``` which eliminates the need for random hashes.

It's the same issue with the default CSS Module setup: makes it hard to debug. http://kevinsuttle.com/posts/css-modules-a-review#local-by-default-is-a-double-edged-sword

Feel free https://github.com/kevinsuttle/kevinsuttle.github.io/issues/new

Side note: not sure if [this](https://twitter.com/kevinSuttle/status/791326383234543618) would be useful or even _possible_, but I thought I'd bring it up to those with the bigger brains here.

@kentcdodds I'm thinking UI libs probably need to start looking at CSS Custom Properties. https://github.com/facebook/react/issues/6411#issuecomment-252734538

You’re right. I like the last option. Agree it’s more logical. I like tailoring rules based on how frequently a part of code is likely to be used.

FWIW: the standard lib has a `no-for-in` rule: https://palantir.github.io/tslint/rules/no-for-in-array/ Also, it has `prefer-for-of`, but that's still a loop. https://palantir.github.io/tslint/rules/prefer-for-of/ Maybe `ban`? https://palantir.github.io/tslint/rules/ban/

Awesome! Thank you!

Has anyone thought about how this would be defined at the Search Engine level? In terms of JSON-LD? https://github.com/schemaorg/schemaorg/issues/944

Works.