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

Possible to generate docs for unpublished code? #9

Open
techieshark opened this issue Jul 15, 2016 · 3 comments
Open

Possible to generate docs for unpublished code? #9

techieshark opened this issue Jul 15, 2016 · 3 comments
Assignees

Comments

@techieshark
Copy link

I've generated a documentation.json file using elm-make --docs=documentation.json and can preview it using this tool, but I'd like to have a local copy of it (this code is part of a web app in development and it doesn't make sense to publish these modules, so getting the code in Elm's online documentation isn't sensible).

I'd like to include this in doc viewers that take docsets, like Dash or Zeal.

Is it possible to use your elm-docset tool to generate a new docset that includes an unpublished documentation.json file?

Thank you.

@pdamoc
Copy link
Owner

pdamoc commented Jul 15, 2016

It's not possible right now to generate docs for unpublished code but should not be all that difficult to implement since the script consumes the same kind of information.
For the sake of clarity, do you want the script to generate a custom Elm docset that includes the unpublished documentation OR do you want the script to be able to produce individual docsets based on a documentation.json?

@techieshark
Copy link
Author

Hi Petre,

Either of those options you mention would be fine I think (assuming I could load either in Dash locally -- I wouldn't be trying to upload anything to the public Dash docset collection).

To allow my local documentation to include links from it to standard types (Maybe, Html etc) I assume we'd have to generate the docset for all of Elm, but if it's possible to link from one docset to another then generating just the individual docset for the project would be fine.

Thanks.

@pdamoc
Copy link
Owner

pdamoc commented Jul 15, 2016

I don't know how to add links to other docsets (I don't even know if that's possible)
For now, I'll think about just adding the extra documentation.json to a regular Elm docset and will proceed from there if other needs arise.

Thank you for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants