On Feb 19, 2008 11:08 AM, eliott <eliott@cactuswax.net> wrote:
That is not our only problem with the json interface. Namely, the info() method doesn't work at all due to a slight coding error in patching together the query string.
I made the necessary changes and put them in testing already: e3d5bd40a32b2421197b392add824d328c99d817 cccd21922904d4d56230301bdf9de4e98d9673f9
I also changed the search method to behave the same way the AUR's web interface does, although I think the fulltext search may be superior, it can't search for parts of words which may be a drawback depending on who you ask.
Removing fulltext searching makes it super fail now. Not sure why/how you think these changes make it better.
Searching seems to work fine for me, I'm not sure what changed, but it seems to work as I'd expect it - could you elaborate a tad? All in all, great work guys. The only oddity I noticed is that the fonts don't sync up to the main site, but that's minor.