-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use @classdesc notation #2178
Use @classdesc notation #2178
Conversation
+1 from me. Thanks a lot for the effort @probins! |
Just had a look, I think this is a very useful change. Great work! I think the |
I agree this is a great improvement. Thanks for the huge effort on it @probins! |
it would be good if someone could find time to add a desc for those I list above. I suspect these won't be used very much, but there's not much point having them in the api if people don't know what they're for :-) And I think there should be a rule: no additions to the api without some docs to describe them. |
see #2183 |
Phew! When I offered to add
@classdesc
to classes https://groups.google.com/forum/#!topic/ol3-dev/7l9rQ6W5c7A I hadn't realised there were quite so many. 113 files updated, some using existing description, some new. Some of these are really stating the obvious, but can be changed later as needed.Some of the vector base sources I have left for now, while I work out how they fit together. And some others I have left, as I don't know what they are for or when you would use them. These are:
I added the word 'abstract' to those I consider to be abstract base classes, not usually instantiated in apps. jsdoc does process the
@abstract
tag, but there are issues with this at the moment. In any case, I think these should be differentiated in the html somehow. I'll raise a topic on the list for this.There's a generated output at http://probins.github.io/classdesc/apidoc/