FS#46261 - The JSON endpoint is too limited
Attached to Project:
AUR web interface
Opened by felix (fstirlitz) - Friday, 11 September 2015, 15:31 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 17 October 2015, 13:28 GMT
Opened by felix (fstirlitz) - Friday, 11 September 2015, 15:31 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 17 October 2015, 13:28 GMT
|
Details
The JSON endpoint at /rpc.php currently only allows
searching AUR and obtaining information about packages.
Users wishing to vote, flag, orphan, change keywords or
comment on a package have to either open their browsers or
rely on fragile screen-scraping tools. Even currently
available functionality of the endpoint is quite limited:
you cannot even obtain information by pkgbase or get the
list of keywords for a package.
Ideally, there should be feature parity between the JSON endpoint and the web interface. |
This task depends upon
Doing it via SSH would require configuring an SSH key, even if he registered only because of commenting and voting, and doesn't want to maintain any package.
Voting, commenting, flagging, getting list of voted packages, getting comments, etc.. should be done with a JSON, or msgpack API.
Voting, or flagging from an AUR helper would be cool.
You can also use `aurtomatic` from https://aur.archlinux.org/packages/python3-aur which has the following available actions: adopt, comment, delete, disown, flag, notify, setkeywords, unflag, unnotify, unvote, vote.
I suppose if we did add a writable json endpoint, these tools could be migrated over to that, but as it stands it is hardly impossible to do.