Open GoogleCodeExporter opened 8 years ago
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
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
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
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
Is it expected that the contents of these JSON links start with ]}' ? eg to
pick one at random:
https://android.googlesource.com/device/ti/panda/?format=JSON contains the
following:
]}'
{
"name": "device/ti/panda",
"clone_url": "https://android.googlesource.com/device/ti/panda"
}
Original comment by most...@opera.com
on 4 Jan 2016 at 9:23
Yes. It's there to prevent using eval. See
http://stackoverflow.com/questions/3146798/why-do-people-put-code-like-throw-1-d
ont-be-evil-and-for-in-front-of
Original comment by fbeauf...@chromium.org
on 4 Jan 2016 at 9:29
Original issue reported on code.google.com by
dborowitz@google.com
on 11 Apr 2013 at 7:31