One of the new links on the Add-on details page is "Add to Collection." See location and layout on these mockups:
And see the interaction flow here:
This bug is for the full implementation of this widget on detail pages and on listing pages. Remember scalability was an issue when dealing with this widget in remora. Don't forget unit tests for things like "This add-on is already in the collection, show it as checked." See the spec for details, section "Add-on Details page": https://docs.google.com/Doc?docid=0Acwo2Bn17-PrZGZudHRobnJfNjVjYnFqMm5kZw&hl=en
In what way was this a scaling issue for remora?
For most people it'll show the login prompt, for the logged in people we should be able to power this all via AJAX.
The scaling problem came from us showing all the user's collections, and then taking out any collections that the add-on was already a part of. It looks like we're doing the same thing here, so we just need to make sure that query is as fast as it can be.
Loading this via ajax wfm.
Code is being reviewed by potch, and then will be styled by him too:
I might use event delegation to avoid re-attaching handlers, but I haven't decided yet.
This is pretty much done, but needs styling.
We disabled this on both preview/next, where it wasn't doing anything (404s).
was zamboni serving these urls?
(In reply to comment #7)
> was zamboni serving these urls?
No. We blocked this code with the NEW_COLLECTIONS flag since we can't run the EB collection migrations on prod and I don't know how the backend will work without it.
QA: There's nothing broken about this bug. We just need to flip NEW_COLLECTIONS to get it back.
Verified FIXED (implemented).