Naming collisions in AngularJS definitions -
i'm trying organise angular application in such way scale appropriately enterprise level. i'm finding there seems over-reliance on naming conventions within framework, , trying avoid naming collisions real issue.
for example, when defining constants
/ controllers
/ directives
/ factories
/ filters
/ providers
/ services
, name supplied implicitly used during dependency injection.
this works great few definitions. when there hundreds (maybe thousands) of these definitions, trying manage , prevent duplicates seems bit of maintenance nightmare!
another issue naming of directives. there doesn't seem way apply context directives, not possible have following (i.e. reuse name "button"):
<toolbar> <button></button> </toolbar> <customform> <button></button> </customform>
therefore again reliant on verbose naming conventions. if include recommended vendor prefix, end this:
<company:toolbar> <company:toolbar-button></company:toolbar-button> </company:toolbar> <company:customform> <company:customform-button></company:customform-button> </company:customform>
which admit isn't horrific, highlights how reliance on naming conventions can cause collisions.
is there on angular roadmap address problem of namespacing, , current (1.0.6) recommended solution problem?
i don't think there solution right now. it's issue apps larger, or when have include arbitrary modules may not known @ dev-time. recommend filing issue angular project.
Comments
Post a Comment