Skip to content
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

Plans to support HTML in the WASM / JS implementation? #513

Open
nberlette opened this issue Mar 6, 2024 · 0 comments · May be fixed by #658
Open

Plans to support HTML in the WASM / JS implementation? #513

nberlette opened this issue Mar 6, 2024 · 0 comments · May be fixed by #658

Comments

@nberlette
Copy link

Hey Deno Team,

I'm curious if there's any plans on the horizon to support HTML docs generation from within the WASM/JS implementation. Not sure if this is even possible... so forgive me if I sound like a noob, but being able to generate HTML docs programmatically would be a dream come true.

My primary need for a feature like this is probably a bit niche. But it's for a custom GPT I'm currently working on, which uses an external API endpoint to provide users with the in-chat capabilities to format users code, write them a README, and hopefully generate a static HTML site for their documentation.

The API endpoint runs on Deno Deploy, so it goes without saying I don't have access to the CLI features. I've got the formatting worked out with the deno_fmt module I published somewhat recently (forgive the shameless plug), but the HTML docs aspect of it has me a bit stuck. Having a feature like this would save me quite a bit of time and energy, so I don't have to re-invent the wheel and write my own HTML codegen from the deno doc JSON.

I assume it would have to be outputted similarly to the doc() output, or the transpile() output from deno_emit (mapping file paths to code), since accessing the local file system would be out of its scope.

Like I said, not sure if it's even possible. My knowledge of Rust is severely limited, but I'm looking to fix that this year 😜.

Anyway, that's enough rambling. Thank you for your time!

@crowlKats crowlKats linked a pull request Nov 8, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant