-
Notifications
You must be signed in to change notification settings - Fork 240
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
Documentation coverage #666
Comments
The truth is that JSDuck is not really maintained any more. So less than
unlikely to happen.
28.02.2017 19:39 kirjutas kuupäeval "Predrag Stojadinović" <
notifications@github.com>:
… Any plans on adding documentation coverage reports, like this one from
esdoc <https://doc.esdoc.org/github.com/esdoc/esdoc/source.html>?
'Cause that would be awesome!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#666>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHNuThDGU2Dyz6KIsp_jeJz-doSbHoAks5rhFuygaJpZM4MOs88>
.
|
Is there a successor? Is there something different that Sencha is now recommending? I've been using this for 3 years and remain pretty happy with it, but always happy to look at other projects. |
What is Sencha using for documentation now? |
My guess is that they're still using JSDuck under the hood to extract docs from source code, but have built a new UI for showing the docs. But these are just guesses. I'm not in contact with Sencha any more. |
It appears this forum thread is related to this question
|
PS: it appears there is some undocumented tool available via SenchaCmd called doxi |
Yeah; I saw that. However, it only outputs JSON, and leaves it to you to build the HTML. I rather like the JSDuck HTML; its part of why I use it (I'm not developing using a sencha JS framework). I don't currently have time budgeted to design and build an entire HTML generator that is as good. This project still works; hopefully they'll have open sourced everything before this starts to break down. |
The problem I have with JSDuck currently is that there's no new release which would fix some bugs like #491 :-( |
Any plans on adding documentation coverage reports, like this one from esdoc?
'Cause that would be awesome!
The text was updated successfully, but these errors were encountered: