(A) Although, I thought `info` lookups had been converted to return Arrays as well.
If not, might I resuggest the merging of `info` and `multiinfo`? Fuse them into just `info`, and return any number of results as an Array, given any number of arguments, also including the ability to search by pkgbase. On 12 August 2014 21:56, Xyne <[email protected]> wrote: > Hi, > > The RPC search, info and multiinfo methods return no data when the pkgbase > is > passed as the argument. > > I would like to discuss the following ideas: > > A) Return all of the packages in the pkgbase for search, info and multiinfo > queries. For search and multiinfo this would be natural. For info it > would be > left to the client to detect that the result is an array instead of an > object and thus infer that the result is from a pkgbase (or simply add > that > data to a new field in the result object). With the advent of the query > version parameter this should not be an issue for backwards > compatibility. > > B) Add a parameter to query pkgbase data (e.g. object=pkgbase) and return a > JSON object with pkgbase-specific data (everything that still applies > from > regular package data, plus an array of the included packages). Given > that > there are AUR pages for pkgbases, it would be consistent to provide that > data via the RPC interface. > > I believe this would be very useful. What do you think? Would it be > difficult? > > Regards, > Xyne >
