Use new version of bem-tools-create

[veged]

Close #12

[awinogradov]

@tadatuta can we already use bem-create by level templates?

[tadatuta]

@awinogradov

can we already use bem-create by level templates?

not sure what are you asking about but this PR looks good to me

[awinogradov]

I mean we want to use different templates for different levels Best regards Anton Winogradov [email protected]

…

On 19 May 2017, 21:06 +0300, Vladimir Grinenko ***@***.***>, wrote: @awinogradov (https://github.com/awinogradov) > > can we already use bem-create by level templates? > not sure what are you asking about but this PR looks good to me — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub (#13 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AA78OJyqKPigGEgvRNVhknZEVq_9XkQ8ks5r7do3gaJpZM4MpMUq).

[tadatuta]

yes, it should work

[veged]

@tadatuta we fix templates and try to do bem create Test (which create all as suppose) and bem create -l blocks/Test/Test.tests simple (which do not create anything) — looks like 'blocks/**/*.tests' in .bemrc.js do not match and affect creation

[tadatuta]

@veged that's true 'coz current implementation of glob expansion uses glob module which looks for real folders on FS.

I created bem-tools/bem-tools-create#52 to support current case but can't say if it can be implemented soon.

Right now the only way to go is to create blocks/Test/Test.tests manually or add it as one of the block's tech (so that bem create Test call with create Test.{css,js,tests}).

[veged]

@tadatuta actually there is the similar problem if directory blocks/Test/Test.tests already exists — bem create will create only default techs (not ones those configured for 'blocks/**/*.tests')