-
Notifications
You must be signed in to change notification settings - Fork 567
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
Request: "gopherjs doc" command #556
Comments
Related issue and PR: golang/gddo#342 Given that's done, can you elaborate what exactly are you looking for? What problem are you trying to resolve? |
I guess I hadn't remembered all the details of those bugs/PRs, despite my involvement in them. It does accomplish what I had in mind, by use of |
Maybe it would be worth considering making |
That's worth considering, because it's very low extra maintenance cost and doesn't deviate us further away from normal Go. We currently do that for |
I'll see about throwing together a PR for that then, since it does sound quite simple. |
Let's decide that we want to do this, since we're still on the "considering" stage. The implementation is indeed trivial. @neelance What do you think about this? |
Sure, why not. It is useful and it adds no complexity. |
Having GopherJS-specific versions of 'go doc' and 'godoc' would be nice.
This could possibly help address the documentation issues mentioned here.
An effectively duplicate feature request already exists on godoc, to support build tag in the official godoc package. But until that's accomplished, supporting it here might be worth while.
Thoughts @neelance , @shurcooL ? If it's deemed a good idea, I may try to work on this myself.
The text was updated successfully, but these errors were encountered: