Suggestion rename helper from "elem" to "bem" about ember-cli-bem

[nikityy]

@urbany well, you're not the first one who suggests renaming. I agree that the name 'elem' might seem confusing. 'What is that 'elem' about? An HTML element?' — would be the first thought in mind of a person who's barely known with the BEM methodology. Names for BEM entities (block, element, modifier) were chosen poorly for my taste, because at least block and element have different meanings in HTML.

So, what was I thinking about when I named this helper 'elem'? Something like that way. If I give it name like 'bem', no one will guess that the helper generates exactly an element class name (not block name). 'bem-elem' looks much better, but it's four characters longer than just 'elem'. So I chose 'elem' name as a compromise between length and explicity.

If helper name seems too implicit, you can re-export helper with any name and contating the following code:

// app/helpers/bem-elem.js
export { default } from 'ember-cli-bem/helpers/elem';

And you will not have to wait until I rename it.

But once again, elem name seemed fine for me, not anyone else. If there's 99% developers who prefer 'bem', I will rename it. Please if you have the same point of view as @urbany does, please vote up or leave a comment here so I can estimate the importance of the renaming. Thanks all.

[exeto]

Adding a modifier through an helper called elem causes cognitive dissonance. It is better to use the bem name.

// app/helpers/bem-elem.js
export { default } from 'ember-cli-bem/helpers/elem';

It doesn't work in 1.0.0-beta.3 version