-
Notifications
You must be signed in to change notification settings - Fork 778
API endpoints for Annotate, History, file listing #3042
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
Comments
Hello,
|
Yes, it captures the current state. We don't really play the API versioning game. It is versioned in Git :-) As for the synchronization, in theory it should work both ways - whatever is edited on Apiary gets propagated to the Github repo (https://github.com/oracle/opengrok/blob/master/apiary.apib) and vice versa. |
Well, exposing "every feature" would be probably too much :-) What are you after specifically ? |
@vladak @tulinkry Thanks for the quick turnaround!!! Here are the descriptions:
(2) "Annotate" endpoint. When I click the annotation, it returns the annotation with the line
(3) FileStructure endpoint: Returns the file structure (Input: filename) Input: "filename": "/android-4.2.2_r1.2/external/webkit/Source/WebKit/chromium/test/CCThreadTaskTest.cpp"
(4) History endpoint: Returns the history of the file. (Input: filename) (5) History of CL/Annotation endpoint: Returns the history By CL(ChangeList number or Annotation). |
@vladak If you can ship these 5 endpoints, it will be super awesome. But if you guys have other priorities for the next version, I can probably raise a PR for this. Can you please provide an instruction/documentation like where to edit the file..? I see Thanks a lot |
The API implementation lives under https://github.com/oracle/opengrok/tree/master/opengrok-web/src/main/java/org/opengrok/web/api/v1, the Python source is merely a consumer. |
Out of these, only the search endpoint is implemented, see https://opengrok.docs.apiary.io/#reference/0/search/return-search-results ; it has its quirks (#2834, #2612). The rest should be reasonably easy to implement. Note that pages served by the webapp should be XHTML compliant and therefore parseable. |
I'd suggest to create separate issue for each of the requested endpoints and we can hash out details there. |
..like #3044 for history API. |
The Not sure what is meant by:
so I did not file new issue for this. |
@vladak GREAT to hear that!!! Thanks a lot for the quick turnaround. I'll follow up w you later next week. I'm occupied for other works now :) Thanks a lot for the help |
The 1.3.9 release has some of the suggested API endpoints. |
The 1.3.10 release has the annotate API endpoint. |
Looking at the API documentation for Opengrok here (https://opengrok.docs.apiary.io/),
I'm building a Frontend web application that can talk with OpenGrok API.
I see History, Annotate and the file detail page such as http://androidxref.com/9.0.0_r3/xref/frameworks/base/packages/Keyguard/proguard.flags promising.
Thanks a lot!
The text was updated successfully, but these errors were encountered: