[Feedback] #167

Checklist

• I have prefixed the issue title with [Feedback] along with a message pointing to the route or feature tested.
  • Example: [Feedback] /packages/{name}
• I have completed the Changes section.
• I have completed the Bugs section.
• I have completed the Improvements section.
• I have completed the Summary section.

Changes

Some notes utilize this database file (db file generated via schema/gendummydata.py).

• Order of JSON isn't the same as in Python. This doesn't really bother me from a usability standpoint though.
• /rpc/ contains a redirect to /rpc in FastAPI but not in PHP, which could be problematic for clients not set up to handle redirects (not sure how many, if any, AUR clients behave in such a way though).
• On PHP, /rpc?v=5&type=search&by=maintainer returns a No request type/data specified. error, but on FastAPI it still shown orphaned packages. Appending ?arg= returns the same results on both implementations. I found this to be a positive change, though I'm not sure what's wanted for backwards compatibility.

Bugs

• (Uses db file) Testing against /rpc?v=5&type=search&arg=me showed a degradation in performance on the FastAPI version. This can probably also be tested by just using a tiny arg= query as shown in this request.
• /rpc/ doesn't bring up the help page on FastAPI, but rather a response from the RPC interface itself stating Please specify an API version..
• Local testing shows a blank white page for the RPC help page on PHP.

Improvements

No improvements noticed, though there wasn't much to improve on outside of speed.

Summary

The search and info endpoints described at https://aur.archlinux.org/rpc/ were tested.