ubuntu-appstore-developers team mailing list archive
-
ubuntu-appstore-developers team
-
Mailing list archive
-
Message #00785
Click package index and architecture restrictions
Hello all!
I'm writing to sync up about click package searches and architecture
restrictions.
There are mainly 2 issues:
* the index is returning unexpected results when passing more than one
arch, so we are gonna change that and return Bad Request if the search
query has more than one architecture definition
* when no arch is given in the search query, only the apps with
architecture: 'all' are returned. Martin mentioned this is not the
expected behavior because:
17:32 < beuno> There may be a use case to not pass in arch, and have
that return results regardless of arch
17:33 < nessita> beuno, right, we already handle that and return all
apps with arch set to 'all'
17:38 < beuno> nessita, well, "all" is an arch
17:38 < beuno> as in, it's arch independant
17:39 < beuno> not passing anything would return everything
17:39 < nessita> beuno, that is not the current behavior
17:39 < nessita> not passing anything returns only the apps with arch 'all'
17:40 < beuno> nessita, k, so that's something to talk to jayteeuk
about. The client may be implemented in a way where that's not easy to
change
17:40 < beuno> the use case also doesn't matter that much
17:40 < beuno> but for browsing the store from a website, for example
17:40 < beuno> without being logged in
17:40 < beuno> we wouldn't know what arch to filter by, and would want
to return everything in the store
Currently the search results do not return the arch info, so a
searches with no arch will return information that will require a new
query per result to be able to show archs to clients, so once we
change the behavior when no arch is sent in search queries, we should
be returning the arch in the result.
How many times did I write arch? :-)
Let me know your thoughts.
Cheers, Natalia.
Follow ups