Aljeksej Jaroševič
Aljeksej Jaroševič
:+1:
I wanna say that there are big difference between `blocks/block/**` and `blocks/block_**`. So you can't emit block-objects in a middle for flat scheme. I think it's fine for small projects,...
> For big projects should use the nested scheme. It would be enough to use any scheme with files grouped by block name.
Can we try to make it? We really need it for watch or partial scan and there are no other options to do it ;-(
Related #39
Okay, let's move to #16 then.
@andrewblond If you've made #16 this task will go higher to builder or level-configurator. What's for we need it in walker?
I think better to just make a `stop` method («горшочек не вари») used to prevent further walking. **upd** I'm not sure that this issue is critical because of #20
`walk(['common.blocks', 'desktop.blocks']).on({ block: 'button' })` — are you sure you really need this? What is the case to use that? What if this block uses another block?
> Isn't it more common for streams to have special events for each kind of thing we're looking for? There is issue #21 about it