This repository has been archived by the owner on Jan 23, 2022. It is now read-only.
feat(): Support for documenting controllers and capitalized services, prettyprint custom usage examples #83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Angular doesn't prohibit this, and neither should the documentation system. This change does require capitalized `Type`s to be explicitly declared, although I can't find any instances of end-users relying on ngdocs to implicitly sniff out Types based on capitalization alone...
Supports controllers. Also supports services with syntax `@ngdoc mymodule.something:MyService`
m7r
pushed a commit
that referenced
this pull request
Apr 14, 2014
feat(): Support for documenting controllers and capitalized services, prettyprint custom usage examples
|
How to use the controller syntax please ? Thx |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In general, I don't think it's a very good idea to sort components in sections based on their module path. In some cases, I've changed the generator to use the type mentioned in the
@ngdocinstead.