-
Notifications
You must be signed in to change notification settings - Fork 25
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
Snippit maintenance / automatic doc generation #15
Comments
@sindresorhus you originally brought up this point. After over a month of work on it, I think I've got this problem pretty well wrapped up. I'd love to get your present feedback / advice on it. If you have a second, could you try this out: $ npm install -g wat
$ wat tour This will walk you through what @wooorm @Qix- @anko feedback from you guys as well would be awesome! |
It looked neat, then I got to generating the chalk docs, which exited with
I installed wat as root but am using it as my own user. Does wat try to cache in its install location? (If so, requesting |
@dthree First of all, very nice work! From what I tried, wat was really useful and I plan to use it in my flow in the future 👍 I found some funky things going on with mdast. I probably have some weird documentation preferences, so I can imagine that having to do with it. Let me know if you have suggestions regarding that! |
@anko aah I see what happened. 99% of the writes go to a temp dir - that write that errored there is something I was going to fix, didn't realize it would create that problem. Should be handled today! Anyway, if you run it as |
@wooorm thanks!! On mdast, yeah I saw that. I just added like 10 more libs yesterday, so I have to go through and tune the autodoc generator to hit more edge cases. The main sit is recognizing what is and isn't an API syntax declaration. I'll probably end up fine-tuning about 30 or 40 libs before I release it. Happy you find it useful though, and suggestions are accepted! |
👍 |
@anko just did a mongo refactor that migrates all writes to the temp directories. I think I got everything. Would you mind re-installing and trying the tour again? |
@wooorm I managed to clean up the autodoc response of |
Looks better, but still some problems, I listed some points I found in GH-23. |
@dthree Aaa, now I get
Anything I enter says "there's no command like that". Is there perhaps a cache I haven't deleted that's giving me a dirty install?
|
Did you just do a fresh install? Try the
This should re-index you. But I'll check that out. I need to make a nuke command or something that destroys the local files. |
@wooorm @anko @tomByrer @octalmage @defel @Qix- just finished the Wiki docs for adding auto doc content to Wat. Adding a library should be incredibly easy and take 10 minutes or less, so I want to make sure my docs are intuitive and reflect that. If you guys are able to, would you mind reading this Wiki and seeing if you can successfully do a PR on a new doc set? You can just pick any library you love. If anything's confusing, I'd like to know now, not when I release it :) https://github.com/dthree/wat/wiki/Docs-|-101 Thanks!! (and btw I'm thanking all contributers directly on the readme) |
For intro comments, see 419654c
The text was updated successfully, but these errors were encountered: