touch-packages team mailing list archive

[Facundo Batista <facundo@xxxxxxxxxxxxx>]

Public bug reported:

Right now the Music scope uses  the categories id from Grooveshark as
part of the mechanism to aggregate results.

But the categories id of remote scopes are only consistent between the
categories and corresponding results. So it should stop relying on those
ids.

If the Music scope needs to know which categories Grooveshark return and
where, we should implement a more robust mechanism.

** Affects: unity-scopes-api (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1398788

Title:
  Music scope should stop relying on Grooveshark internal category ids

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Right now the Music scope uses  the categories id from Grooveshark as
  part of the mechanism to aggregate results.

  But the categories id of remote scopes are only consistent between the
  categories and corresponding results. So it should stop relying on
  those ids.

  If the Music scope needs to know which categories Grooveshark return
  and where, we should implement a more robust mechanism.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1398788/+subscriptions