-
As a developer of this API
I want to easily find the generated docs based on the JSDoc comments with the code
and this should be automated
so that no developer needs to manually generate and uploa…
-
I think it would be useful to add JSDoc to the project. It would be easier to contribute and you could generate documentation automatically. What do you think?
-
There's a lot to do there.
-
prepare the sdk to be scanned by jsdoc, highlighting the main helper functions
-
This repo is missing a lot of JSDoc, I have no idea what anything means because I love JSDoc, and all forms of documentation and cannot see without it.
I'll add some.
-
I noticed eslint has a plugin that verifies jsdoc. Should we evaluate it for potential PhET usage?
https://github.com/gajus/eslint-plugin-jsdoc/blob/master/README.md
-
* Document missing JSDoc
-
### Issue summary
Update JSDoc to follow the standards outlined in the [Google JS StyleGuide](https://google.github.io/styleguide/jsguide.html#jsdoc) and the [JSDoc documentation](https://jsdoc.app…
-
This is a great tool for those of us that religiously comment our code. Would be awesome if it parsed JSDoc in some way, maybe just adding some basic formatting.
-
The return type of `analyzeCommits` is declared as `String|null` in the JSDoc header. However, `analyzeCommits` is an async function. Return type should be `Promise` instead.
https://github.com/sem…