Closed Bug 937281 Opened 12 years ago Closed 10 years ago

Create API endpoint to manage "heart"s for search results

Categories

(Marketplace Graveyard :: API, enhancement, P5)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: chuck, Unassigned)

References

Details

Let's create an API endpoint to manage hearts for search results. - Authentication required. - /api/v2/heart/search/<slug> - POST to heart, DELETE to remove the heart - Should be behind the waffle switches created in bug 937246 and bug 937248 - There should also be an additional field on search results specifying a query indicating whether the authenticating user has hearted that category. - Documentation
What exactly would a "search/<slug>" be? Is someone going to set up some search keywords in the database and assign them a slug that we surface in the feed?
<search-terms> would have been more appropriate than <slug>; we'd treat them as an slug/identifier of a pseudo-resource, in the absence of an actual resource representing them. In a hypothetical Heart model, I expect the field for this to be a simple TextField.
Priority: -- → P2
Severity: normal → enhancement
Priority: P2 → P5
No longer blocks: feed-v1-api
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.