Hacker News new | ask | show | jobs
by calebegg 4092 days ago
I don't think it's exactly a hard and fast rule, but our team does not use the "ng-" prefix for custom components, since the purpose of the ng- prefix is to avoid naming conflicts between Angular builtins and custom directives (and built-in HTML attributes/elements). So it might be good to call this something else, at least in the code.
1 comments

Author here. Yea I was not sure on the best approach for naming when using the directive in template but when specifying it as a dependency the directive is referenced by `ui.dial`.
+1 on namespacing. You want to pick your own prefix and use in both places - for example: gmd-dial and gmd.dial

'ui' is used by AngularUI: https://angular-ui.github.io/

Otherwise, once the dialer angular component explodes, and AUI comes out with their own competing directive, a client programmer using both yours and AUI's modules will have a problem.

Thx. I'll update accordingly here.