-
Notifications
You must be signed in to change notification settings - Fork 7
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
externally consumable REST API #48
Comments
+1, this will be an extension of the current API Existing REST APIs:
Ideas:
Please add ideas |
The current "API" search-like call |
As an idea, also the real search |
Especially the projects could use pagination (1-based, default size 100): |
What is returned by
|
Results lists could be accompaned by the results size:
|
Is there a strong reason to have some fields prefixed with an underscore? |
Errors objects should be standalone reply objects - not just cram error messages inside regular answers like this answer from
|
underscore prefix explanation: we're adding these elements to existing JSON structures received from various APIs. The underscore was a convention to easily identify these attributes. Alternatives welcome |
Ok fine with the underscores - how about we also document why :) |
Creating an external user specific REST API ,whereby OSSRank will provide ranking and other metadata to outside world
The text was updated successfully, but these errors were encountered: