Set up a tastypie - django REST framework compatability layer

RESOLVED FIXED in 2013-06-06

Status

Marketplace
API
P3
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: andym, Assigned: andym)

Tracking

2013-06-06
x86
Mac OS X
Points:
---

Details

(Whiteboard: [qa-])

(Assignee)

Description

4 years ago
Set up a tastypie - django-rest-framework compatibility layer so that we can transparently swap out things and plonk in rest-framework.

This means making the:
- paginator
- 500 errors
- 400 form errors

The same between the two.

And finally write some docs and examples for developer so they know what to do.
Summary: Setup a tastypie - django rest framework → Set up a tastypie - django rest framework

Updated

4 years ago
Summary: Set up a tastypie - django rest framework → Set up a tastypie - django REST framework

Comment 1

4 years ago
Perhaps it would be better to make a v2 of the API and port the functionality of each endpoint over one by one? If we're moving to DRF, it would be simpler on the front-end to port one view at a time than it would be to port one feature at a time. I'd think that it would make a lot of things cleaner in the long run, as well. Thoughts?
(Assignee)

Comment 2

4 years ago
Once the layer is in place its a matter of porting one view at a time. If would rather do this and have it be transparent for solitude, curling and everything else too. And I did most of it on the plane last week.
Summary: Set up a tastypie - django REST framework → Set up a tastypie - django REST framework compatability layer
(Assignee)

Comment 3

4 years ago
r? https://github.com/mozilla/solitude/pull/94

Start for solitude, will port over.
Target Milestone: 2013-05-30 → ---
(Assignee)

Updated

4 years ago
Target Milestone: --- → 2013-06-06
(Assignee)

Comment 4

4 years ago
https://github.com/mozilla/solitude/commit/6cb37f
(Assignee)

Comment 5

4 years ago
https://github.com/mozilla/zamboni/commit/fbcb29
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.