-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Provide a generated API documentation #946
Comments
@mootari Thanks for the issue! If you're reporting a bug, please be sure to include:
If your issue is related to one of the following, please open an issue there:
|
JSDoc might have a bit of a problem with factory functions though (jsdoc/jsdoc#1086, jsdoc/jsdoc#1244). |
Oh boy, that's a deep rabbit hole ... both |
Also, function arguments are consistently wrapped in backticks. While jsdoc doesn't complain about them, they still need to be parsed out (which can probably be done on the template level). Low priority, though. |
Before going down the JSDocs path any further, we use verb for generating our documentation and have talked about module inheritance for the docs. I'm on my phone right now but I'll try to link to some of the libs I'm referencing when I get back to the computer. |
@mootari here are the pieces that we use for building docs:
|
In that case I'll be shifting my focus towards creating TypeScript definitions for some of the packages. That should prove to be a good starting point regardless of what direction will be taken later on. |
Dropping some stuff here for reference: All dependencies, sorted by author
(Almost) all dependencies that have type definitions
Selection of potentionally relevant dependencies with type definitions
Edit: Yup, that's almost 250 packages by @jonschlinkert and @doowb. I dearly hope most of those are internals. :) |
FWIW I've been working on a number of huge improvements to how comments are parsed and used to create API documentation. You will be able to customize a lot more, and one of the goals is to offer support for JSDoc conventions.
Awesome thanks! that would be greatly appreciated.
Lol, yeah there is way too much focus in node.js on the number of dependencies. There is very little to no difference in load time between local dependencies ( |
Sounds exciting, please keep me posted! Which repos should I watch?
I'm merely worried about the number of packages I might have to sift through and create definitions for. ^^ |
Ah! Indeed, the vast majority of those libraries are not directly related to Assemble. Many of them are generic utility libs used by other libs. |
Assemble's highly modular nature makes it difficult to discover methods that are added via mixins or inheritance. For example,
.use
and.define
are provided byBase
and implicitely added throughTemplates
.It would be a huge help to have some basic, generated JSDocs that incorporate all of the default packages. JSDoc provides the
@mixin
and@mixes
annotations which could potentially help a lot to compile docs with minimal effort.What are your thoughts (or plans)?
The text was updated successfully, but these errors were encountered: