Status

Input Graveyard
Code Quality
RESOLVED WONTFIX
3 years ago
a year ago

People

(Reporter: willkg, Unassigned)

Tracking

Details

(Whiteboard: u=user c=api p= s=input.2015q4)

(Reporter)

Description

3 years ago
edwin-input
The API endpoints in Input vary greatly in their output. That's kind of irritating because it's inconsistent which makes it less predictable and harder to follow.

This tracker covers fixing all the APIs in Input to be more consistent.

First we should come up with and document the standard.
Depends on: 1166457
Depends on: 1166458
Depends on: 1166459
Depends on: 1166460
Grabbing this now to figure out the standard and document it.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Also, if we end up going with django-filter, we can use this:

http://www.agmweb.ca/2015-05-11-stricter-filtering/
Depends on: 1132455
Whiteboard: u=user c=api p= s=input.2015q2 → u=user c=api p= s=input.2015q3
New quarter!
Whiteboard: u=user c=api p= s=input.2015q3 → u=user c=api p= s=input.2015q4
I'm unassigning myself from this. I'm not going to get to it before I transition off.
Assignee: willkg → nobody
Status: ASSIGNED → NEW
The Input service has been decommissioned (see bug 1315316) and has been replaced by a redirect to an external vendor (SurveyGizmo). I'm bulk WONTFIXing Input bugs that do not appear to be relevant anymore.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
(Assignee)

Updated

a year ago
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.