-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Autogenerate JS Core API Docs #4021
Comments
The end goal was always to use https://typedoc.org/ to gen the docs, we didnt do it because the output wasn't always the best because of legacy cjs code. |
I think this might be a pretty interesting task for one of our Dev Productivity Launchpad Cadets. According to the schedule, they'll start working on issues after Feb 21. Would that timeline work here? |
👋 I took a quick shot at this issue to try to move it forward, without much success yet, It's not straightforward to point typedoc to There is a monorepo configuration with typedoc, but I couldn't get it to work. It looks like our setup confuses typedoc: it tries to load our I did manage to generate an equivalent of the current doc by pointing typedoc at the
I see a few options:
Notes with all the commands & experiments I ran: https://gist.github.com/laurentsenta/aa7c70a0b83880abe9b6ad0ffd34d488 |
Laurent, are you planning on taking this on? |
@SgtPooki Not right now, feel free to take over, |
js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide. Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterward (see #4336). |
Problem
Right now JS Core API docs are maintained by hand as a directory with bunch of Markdown files.
This is unsustainable, docs often get out of date (#4013, #3990, #4014, #3911, etc), wasting everyone's time.
Proposed solution
cc @achingbrain @BigLep + @hugomrdias if there is any prior art for doing this in JS land
The text was updated successfully, but these errors were encountered: