-
Notifications
You must be signed in to change notification settings - Fork 65
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
Better docs for parser options #10
Comments
If you would allow it, after the typescript fixing, we could set this up in Then tutorials could be in-boarded and there would be a very clear single place from which to teach |
I'm open to using tsdoc, but I'm not ready to move the whole project to ts to get it, and the current mechanism of hand-maintaining the |
You don't need to. Also, you really ought to: when I already did it, I drove more than 100 bugs out of
It's a one-liner with
Will do. Probably next weekend - I mostly can only find time for open source on the weekends right now. It's actually a pretty easy lift, you'll see. Basically all you do is turn Granted you have some bugs to fix then, but that needs to happen anyway |
Nod. I've gotten the first few bits of that working in a few other projects, but had to use jsdoc type annotations, which:
I'm looking forward to seeing how a |
meaning bug 666 about setting context data at runtime? i was just talking about documentation generation |
OK, I'll start a different bug for doc generation, and fix this one tactically for now. |
See #87 |
…clear that you can pass in anything you want to options.
…clear that you can pass in anything you want to options.
There at least needs to be an example
See: pegjs/pegjs#666
The text was updated successfully, but these errors were encountered: