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
Summary: Set up a tastypie - django rest framework → Set up a tastypie - django REST framework
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?
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
r? https://github.com/mozilla/solitude/pull/94 Start for solitude, will port over.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.