Amazon scope doesn't respect user navigation, returns a parent not where the user came from, but what Amazon backend indicates

Bug #1403072 reported by Facundo Batista
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Rest Scopes
Won't Fix
Medium
Unassigned

Bug Description

To reproduce it...

- go to amazon scope
- baby products (see which department id is returning in the tree for "Categories": Baby:165797011)
- categories
- baby & toddler toys (see the parent returned in this tree: Baby:165795011)

See how those department IDs are different? They shouldn't.

Moreover, if you hit "back", it currently fails.

More than that, we should respect user navigation, not how Amazon happens to walk the tree. If the user came from "department A", and clicks on a children there, the parent should always be "department A".

Revision history for this message
Facundo Batista (facundo) wrote :

The moment the client requests the tree centered in "baby & toddler toys", the server doesn't have anywhere the reference of where the user came from (and when the server asks for its parent, the different department is returned from Amazon; this is because Amazon departments structure is not a tree, but a graph).

There is one solution for this, though, that is keeping the state of user navigation in the URL returned (that the client will send back); so, instead of the department be named like

   Baby:165762348

It will be more like

  Baby:Categories:165797011:Baby%20%26%20Toddler%20Toys:165762348

And that so deep as the user navigates.

Changed in ubuntu-rest-scopes:
importance: High → Medium
Changed in ubuntu-rest-scopes:
assignee: Facundo Batista (facundo) → nobody
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.