-
Notifications
You must be signed in to change notification settings - Fork 20
add --html-style option #166
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
Conversation
MartinNowak
commented
Aug 9, 2017
- allow to pretty-print HTML output (useful for tests and development)
- quite suboptimal due to support runtime diet traits rejectedsoftware/diet-ng#33
- allow to pretty-print HTML output (useful for tests and development) - quite suboptimal due to rejectedsoftware/diet-ng#33
|
I guess the |
Diffing the test cases for ddox ;). In particular being able to check-in and diff the generated HTML would be useful. I might just change the default for generate-html, but some ppl. might want to statically serve those files. |
|
Being able to temporarily switch back to pretty-print output would be really nice to have for dlang/dlang.org#1891 (upgrading dpl-docs to ddox 0.16) |
|
Okay, should be good to go then. There are only a few templates, so that compiling them twice shouldn't matter much in terms of compile time and memory usage. |
|
Thanks a lot! |
|
I'll have to think about the satellite projects, but my idea for the vibe-d org was to keep it focused on the core components, basically as a replacement for the monolithic "vibe.d" repository. But in the meantime I sent you an invitation to the DDOX developers team (and tagged 0.16.5 ;). |
Okay, but then at least
Thanks a lot! FWIW as we plan to replace Ddoc with Ddox over the next months, we could probably even move it to the |
|
vibed.org I'd agree, diet-ng I'm not sure yet, because in the process of separating it out, it was also made fully independent of any other vibe.d components and I was thinking about giving it its own brand to broaden the scope (I already registered diet-lang.org for that purpose). As to moving Ddox to the dlang org, that would make sense, but I'd postpone that to when it is deemed "finished" (i.e. no big changes are planned anymore). The major change that I have in mind is fully switching to the libdparse based parser to avoid all the issues with DMD's JSON output. |