mustDeps from own modifier is impossible

[tadatuta]

Looks like it's impossible now to have mustDeps from own modifier:

$ ls common.blocks/b1/
b1.deps.js

$ cat common.blocks/b1/b1.deps.js
({
    mustDeps: [
        {
            mods:  { m1: 'v1' }
        }
    ]
})

$ enb make
# ...
Error: Unresolved deps:
b1 <- b1_m1_v1
b1_m1_v1 <- b1, b1_m1
b1_m1 <- b1

// cc @blond @incrop

[tadatuta]

BTW,

({
    mustDeps: [
        { elems:  ['e1'] }
    ]
})

works fine.

[incrop]

@tadatuta I think this is not a bug, you have a circular mustDeps issue here.
Modifier should modify the block, therefore block must be declared before its mods.
In deps tech this is enforced by adding block to mustDeps for mod. This is how it always worked (check this commit from 2013).
Noteworthy, deps-old tech allows you to have mustDeps from own modifier.

[tadatuta]

I understand the idea but still I used to use such possibility with deps-old at least for 2 reasons:

1. To override some styles of a _theme from a library on project level. It's quite safe when you know what you're doing as most likely there's no CSS for block without theme modifier.
2. To set some defaults for non-BEM modules. E.g. in m1_lang_ru.js:

m1.defaults.lang.ru = {/* ... */};

And then I can initiate an instance of m1 in m1.js.

Both of the cases are quite ugly but still they were possible when really needed.

[Guria]

+1, I don't like an implicit deps from block.

[tadatuta]

I asked @veged, he agrees that it's a bug

[blond]

@tadatuta Looks really like a bug. The question is whether you can fix it without breaking habitual behavior.

[blond]

This problem is also relevant for elem mods:

({
    mustDeps: [
        {
            elem: 'e1', mods:  { m1: 'v1' }
        }
    ]
})

Error: Unresolved deps: 
b1__e1 <- b1__e1_m1_v1
b1__e1_m1_v1 <- b1__e1, b1__e1_m1
b1__e1_m1 <- b1__e1

[Guria]

is bem-site/bem-forum-content-ru#182 relevant to this issue?

[blond]

@Guria, I think that this is another problem.