Skip to content
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

Add JSON and TEXT links to more pages #27

Open
GoogleCodeExporter opened this issue Mar 20, 2015 · 4 comments
Open

Add JSON and TEXT links to more pages #27

GoogleCodeExporter opened this issue Mar 20, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link
Collaborator

Ideally, we would offer JSON and TEXT links for every view for which there is 
JSON or TEXT available. Doing this manually in the templates is easy enough but 
is surely the sort of thing we would forget to do. It might be nice to have it 
happen automatically, in which case we would need to teach BaseServlet 
implementations how to advertise which formats they support.

Original issue reported on code.google.com by dborowitz@google.com on 11 Apr 2013 at 7:31

@GoogleCodeExporter
Copy link
Collaborator Author

FWIW, this would be very helpful for the chrome team.  I recently wrote a tool 
which needed to look up commit messages (i.e. from 
https://chromium.googlesource.com/chromium/blink/+/master). I ended up writing 
a regex to parse gitiles html.

Original comment by ilevy@chromium.org on 6 May 2013 at 1:06

@GoogleCodeExporter
Copy link
Collaborator Author

Thanks for the suggestion, we are more than happy to prioritize which JSON 
endpoints we implement first based on Chrome's priorities :)

That said this bug is specifically about the JSON and TEXT link badges you see 
at the bottom of https://chromium.googlesource.com/. Currently we *only* put 
those links on /, even though JSON and/or TEXT are available for more pages.

Original comment by dborowitz@google.com on 6 May 2013 at 9:32

@GoogleCodeExporter
Copy link
Collaborator Author

Having json listing for the recent commits, is the only issue (that I'm aware 
of) preventing us from moving Blink's "garden-o-matic" tool to a server:
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/To
ols/GardeningServer/scripts/svn-log.js&q=svn-log&sq=package:chromium&l=100

I looked at adding it earlier this summer, then got distracted with other 
things.  Eventually I'll get back to it.

Original comment by esei...@chromium.org on 5 Sep 2013 at 4:26

@GoogleCodeExporter
Copy link
Collaborator Author

re: #3
I don't know if this is new since your comment, but does this work for your 
json recent commits listing:
https://chromium.googlesource.com/chromium/blink/+log/HEAD~5..HEAD?format=JSON

Original comment by mmoss@chromium.org on 15 Feb 2014 at 12:57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant