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

Automated docs would be helpful #7

Open
erikjung opened this issue Mar 4, 2016 · 8 comments
Open

Automated docs would be helpful #7

erikjung opened this issue Mar 4, 2016 · 8 comments
Assignees
Milestone

Comments

@erikjung
Copy link
Contributor

erikjung commented Mar 4, 2016

Related to #6

@erikjung erikjung self-assigned this Mar 4, 2016
@lyzadanger
Copy link
Contributor

FYI, I tried doxdox documentation rendering. Despite my relatively robust comments, the output didn't seem too...useful. You're more than welcome to see if you can get it to be a bit nicer!

@neogeek
Copy link

neogeek commented Apr 11, 2016

Hey there, I'm the creator of doxdox and I saw you were looking into using it for this project. I'm sorry the output isn't working for you - I'm actually in the process of writing a new version (with more in-depth documentation) and would love a chance to work with you to improve the output.

@erikjung
Copy link
Contributor Author

Hello @neogeek,

Great work on doxdox. We've only used it on one other project so far, but it's been an enjoyable tool for producing standardized README docs (using the --layout markdown option).

Regarding the output, I believe the only issue we've struggled with is how to use the Markdown layout (outputting to a single file), but with more control over the order things are displayed in.

For a very simplified example, we might have a structure like this:

src
├── helpers.js
└── main.js
doxdox src --output docs/README.md --layout markdown

In the resulting file, the helper functions would come first, while we might prefer them to come last. Aside from renaming files, it would be helpful to be able to specify multiple path arguments (which would be read in series), for example:

doxdox src/main.js src/helpers.js --output docs/README.md --layout markdown

@neogeek
Copy link

neogeek commented Apr 20, 2016

@erikjung: That is a very good point, and something I hadn't considered before. I will look into seeing how easy it would be to add multiple input files through the current CLI. Do you think it would also be useful to create a config file for projects with more than a couple of files?

Something like this:

.doxdoxrc

{
    "input": [
        "src/main.js",
        "src/helpers.js"
    ]
}

@erikjung
Copy link
Contributor Author

erikjung commented Apr 20, 2016

@neogeek

Do you think it would also be useful to create a config file for projects with more than a couple of files?

I can't think of a reason why not :)

I assume the input array would dictate the order of concatenation when the docs are built?

Also, maybe globs?

@neogeek
Copy link

neogeek commented Apr 21, 2016

@erikjung

I assume the input array would dictate the order of concatenation when the docs are built?

Yep. Going to look into adding the CLI feature this weekend and then porting it over to the rebuild.

The config file and glob based pattern matching might need to wait until the next major release (currently in development).

@neogeek
Copy link

neogeek commented May 6, 2016

@erikjung

I have released a new version of doxdox (v0.1.13) that supports multiple files via both the command line script and API.

Let me know if you run into any issues.

@erikjung
Copy link
Contributor Author

erikjung commented May 6, 2016

Thanks @neogeek,

I tried out the multiple path arguments, and it works just as expected 👍

@erikjung erikjung modified the milestone: Future May 26, 2016
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

3 participants