Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Feature requests: JSON/XML format beside plain-text #58

nvcnvn opened this Issue · 3 comments

3 participants

@nvcnvn support plain-text for integration, why not JSON or XML, that sound a better format for that kind of work.
I see you are using two version of template, one for HTML and one for TXT, so I think I not to hard for a json version.

One more thing:
Instead of using a reuqest header, why not just a parameter?
For example:

Thanks for your great project


If somebody has a specific use for a JSON API that fits with the goals of the project, then I'll add a JSON API. I don't want to implement and support features that are not used.

GoDoc supports plain text output because somebody had a use for it. The plain text output works great for integration with shell scripts.

GoDoc follows the HTTP standard for content negotiation. The HTTP standard uses a header.

If you have a specific need for a JSON API, then please open a new issue describing what you need and how you plan to use it.

@garyburd garyburd closed this

I want to add tab completion to the go get command and want to use to build the local index. I'd prefer not to scrape, so a json api would be nice. Let me know if I should open a new issue.


Please start a new issue with a description of the request and responses needed for tab completion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.