Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Sergey Berezhnoy
    @veged
    if b2 have noDeps to b1 it doesn't affect any b1 deps b2
    Vsevolod Strukchinsky
    @floatdrop
    does it affects dependencies in upper levels of declaration (for example bem-core)?
    Sergey Berezhnoy
    @veged
    b2 noDeps b1 affects only b2 *Deps b1
    Vsevolod Strukchinsky
    @floatdrop
    okay, suppose I have b2 in level1 and level2
    and in level1 b2 is dependent on b1
    but I write noDeps in level2
    Sergey Berezhnoy
    @veged
    @floatdrop yes, it affect any levels
    Vsevolod Strukchinsky
    @floatdrop
    okay
    thanks!
    should it be named ignore or exclude then?
    Sergey Berezhnoy
    @veged
    it can be and can not ;-) I'm not a fan of unnecessary renamings
    there are to many synonyms ;-)
    Vsevolod Strukchinsky
    @floatdrop
    what about A shouldDeps B + B shouldDeps C
    and A noDeps C?
    Sergey Berezhnoy
    @veged
    the main problem to understanding is not a name, but the semantic
    Vsevolod Strukchinsky
    @floatdrop
    and reverse example: A shouldDeps B + B shouldDeps C and C noDeps A (in case you are building C)
    Sergey Berezhnoy
    @veged
    noDeps affect only direct deps declaration and doesn't affect any indirect declarations
    Vsevolod Strukchinsky
    @floatdrop
    is is true @matmuchrapna ?
    I heard we are ignoring i-bem with some mods
    from block, that mustDeps i-bem
    So in our case: b-page mustDeps i-bem, i-bem someHowDeps __dom_auto and b-page noDeps i-bem__dom_auto
    I am pretty sure, that it is not direct declaration in our case
    Vladimir Starkov
    @iamstarkov
    @veged also, can you tell how and why noDeps appeared?
    Sergey Berezhnoy
    @veged
    the purpose of noDeps originally was for canceling dependency between b-page and i-bem__dom_init_auto — but after that people find more use cases
    Alexej Yaroshevich
    @zxqfox

    the purpose of noDeps originally was for canceling dependency

    so it's cancelDeps :palm_tree:

    Alexej Yaroshevich
    @zxqfox
    Guys. How you using your libraries in express apps?
    I'm asking because I want a critical response on this https://github.com/zxqfox/express-bem
    Vsevolod Strukchinsky
    @floatdrop
    How does it fetches dependent bemhtml/bemtree files for view from desktop.bloks @zxqfox ?
    @veged - is this case you mentioned as direct dependency?
    Alexej Yaroshevich
    @zxqfox
    It uses already built bundles.
    Vsevolod Strukchinsky
    @floatdrop
    Then you should not mention desktop.blocks under https://github.com/zxqfox/express-bem#directories, am I right?
    (and it should be mentioned in readme somewhere)
    Alexej Yaroshevich
    @zxqfox
    More accurate only .bemhtml.js and .bemtree.js. And yes, you don't need raw blocks in production, only bundles.
    Vsevolod Strukchinsky
    @floatdrop
    (and example, how you can build those files would be nice too)
    What about this package https://github.com/zxqfox/express-bemhtml ?
    Alexej Yaroshevich
    @zxqfox
    To build these files you just need configured project with .bem/*, declared .bemjson.js or .bemdecl.js and execute bem make
    Or enb, if you using it
    This package was a testing plugin with bemhtml tech only.
    Vsevolod Strukchinsky
    @floatdrop
    imho it is better to write express-bemtree and express-bemhtml
    Alexej Yaroshevich
    @zxqfox
    But without bemtree it's like unfinished or uncomfortable
    Vsevolod Strukchinsky
    @floatdrop
    why?
    oh, i got it
    Alexej Yaroshevich
    @zxqfox
    Just 'cause you should pass finished bemjson tree, but in express world usually you passing some params to templates, and template renders it properly
    Vsevolod Strukchinsky
    @floatdrop
    i’m still not sure about name of the package, but nice work
    Alexej Yaroshevich
    @zxqfox
    May be you're right. But there are no other options. And also we must write one more plugin like express-bem-techs and arch will be too complex.
    I think I should remove express-bemhtml package
    Vsevolod Strukchinsky
    @floatdrop
    why whould we?
    Alexej Yaroshevich
    @zxqfox
    Because express waits for name of template and some params ;-) Just like bemtree do. But not like bemhtml, and when we want ready to send html it's much harder to do it without third mixin package
    which calls both bemtree and bemhtml to generate final html