Support short-naming

[belozer]

Now:

block-super-long/block-super-long.css
block-super-long/block-super-long.deps.js
block-super-long/block-super-long.bemtree.js
block-super-long/block-super-long.bemhtml.js
block-super-long/__elem/block-super-long__elem.css
block-super-long/__elem/_modifier/block-super-long__elem_modifier_value.css

Short:

block-super-long/style.css
block-super-long/deps.js
block-super-long/bemtree.js
block-super-long/bemhtml.js
block-super-long/__elem/style.css
block-super-long/__elem/_modifier_value/style.css

[blond]

I think we can add nested-lite scheme that will support only short-naming.

[qfox]

This looks strange.

block-super-long/bemtree.js
block-super-long/bemhtml.js

If tech is 'bemtree.js' then name is empty?

How it should works?

[Guria]

@zxqfox name is folder name

[belozer]

A block is a set of techs and resources.

block -> folder on filesystem

techs and resources located in the block and belong to him

[qfox]

@zxqfox name is folder name

Nope, it can't be by default.

Check it:

const path = require('path');
[
  path.parse('blockname/bemhtml.js'),
  path.parse('blockname/style.css'),
  path.parse('blockname/deps.js')
];
// →
[ { root: '', dir: 'blockname', base: 'bemhtml.js', ext: '.js',  name: 'bemhtml' },
  { root: '', dir: 'blockname', base: 'style.css',  ext: '.css', name: 'style' },
  { root: '', dir: 'blockname', base: 'deps.js',    ext: '.js',  name: 'deps' } ]

P.s. Of course we can always pass a couple of params to customize this logic inside scheme. But is the game worth the candle?

[belozer]

@zxqfox yes.

BEM already very long in HTML.. But for HTML created XJST.
Next step: for FS we can create nested-lite