You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed I need to mark module definitions as belonging to themselves, i.e.
@ngdoc module
@name MyModule
@module MyModule
or I will get error messages saying No MyModule module found, related components:
Looking at Angular's own documentation, for instance for ngResource, they don't do this. Since looking at Angular's stuff is one of the primary ways of picking up the somewhat sparsely documented ngdoc syntax, this can be really confusing for new users (such as me :) )
I humbly suggest either mentioning that this is necessary in the documentation for dgeni-alive, or fixing it so it can live without the @module MyModule when @ngdoc shows a module is being defined. If it helps any, the offending line seems to be in processors/mappers/api.js
The text was updated successfully, but these errors were encountered:
Dgeni assumes that if no module name specified it takes first folder name as the module name. I do not see a good way to avoid setting of the both @name and @module params.
I've noticed I need to mark module definitions as belonging to themselves, i.e.
or I will get error messages saying
No MyModule module found, related components:
Looking at Angular's own documentation, for instance for ngResource, they don't do this. Since looking at Angular's stuff is one of the primary ways of picking up the somewhat sparsely documented ngdoc syntax, this can be really confusing for new users (such as me :) )
I humbly suggest either mentioning that this is necessary in the documentation for dgeni-alive, or fixing it so it can live without the
@module MyModule
when@ngdoc
shows a module is being defined. If it helps any, the offending line seems to be in processors/mappers/api.jsThe text was updated successfully, but these errors were encountered: