[deleted]
Django REST framework 3.1 released
31–40 of 46 posts
Re: Django REST framework 3.1 released
#32I am using this framework for few applications and absolutely love it. Keep it up Tom.
Re: Django REST framework 3.1 released
#33Super useful tool, thanks to Tom and everybody who contributes. When we began moving some of our APIs from Django to Flask at my company, djangorestframework was the single tool/package that I missed most. It's lovely. What are the plans (if any) for continued development on Flask-API?
I'm curious why you decided to move APIs from Django to Flask? We've built our APIs on Flask, and, though I like Flask a lot, the major complaint is that there's no real story around user authentication and authorization, endpoint versioning, and a handful of other things that aren't directly serving the purpose of the API, but are important nonetheless. There are a hodge-podge of plugins to do various things, but th…
I am writing an API right now in Flask, and I chose it over Django never having used Django for a REST service before.
When you say "there's no story" around auth, endpoint versioning, and other things does that just mean that you're not forced to follow those conventions with Flask / that Django offers utilities to help? I am a bit confused/curious what you meant by that since I've seen some wonderful Flask auth work, and endpoint versioning is pretty standard on most APIs, but seems like Django is a bit more strict with what they want you to do.
Re: Django REST framework 3.1 released
#34Earlier quoted context omitted.
I'm curious why you decided to move APIs from Django to Flask? We've built our APIs on Flask, and, though I like Flask a lot, the major complaint is that there's no real story around user authentication and authorization, endpoint versioning, and a handful of other things that aren't directly serving the purpose of the API, but are important nonetheless. There are a hodge-podge of plugins to do various things, but th…
I am writing an API right now in Flask, and I chose it over Django never having used Django for a REST service before. When you say "there's no story" around auth, endpoint versioning, and other things does that just mean that you're not forced to follow those conventions with Flask / that Django offers utilities to help? I am a bit confused/curious what you meant by that since I've seen some wonderful Flask auth wor…
strict in what way? I've built many api's using django-rest-framework and it is truly awesome to work with, completely extensible and flexible and never seems to get in my way
Re: Django REST framework 3.1 released
#35My friend and I just started getting into Django the other day. Coming from Node.js it is a welcome change.
Re: Django REST framework 3.1 released
#36My friend and I just started getting into Django the other day. Coming from Node.js it is a welcome change.
what do you like about it vs node?
Re: Django REST framework 3.1 released
#37Earlier quoted context omitted.
I am writing an API right now in Flask, and I chose it over Django never having used Django for a REST service before. When you say "there's no story" around auth, endpoint versioning, and other things does that just mean that you're not forced to follow those conventions with Flask / that Django offers utilities to help? I am a bit confused/curious what you meant by that since I've seen some wonderful Flask auth wor…
strict in what way? I've built many api's using django-rest-framework and it is truly awesome to work with, completely extensible and flexible and never seems to get in my way
I just meant that they offer more of a base + guidelines for you to work with when compared to Flask's "roll it yourself" approach to REST.
Re: Django REST framework 3.1 released
#38DRF brought me back to Django after a foray into Flask-land. It's a pleasure to work with. Thanks for your work, and to the backers who funded the latest development!
Re: Django REST framework 3.1 released
#39I've started using DRF last week and I don't know why I did'nt use it before.
The authentication framework and the Model serializer are really good points to start, but I was missing some versioning scheme and 1 week later here it comes. Great work, Tom.
Re: Django REST framework 3.1 released
#40Earlier quoted context omitted.
An issue that I've consistently run into is being able to write to related models. I can serialize them just fine, but without being able to write, it forces users to come up with nasty work arounds. To be fair, I hate having to write resources that handle writing nested objects, but there are some many front end use cases where multiple writes is not ideal.
Oh right, writable nested serializations, sure. I won't rehash the reasons that we don't support that in core (ill defined what behavior the user should expect) but yeah it'd still be good to have a third party package that does a decent "best effort" job of that. My personal take on this is forget about "shitty hacks" or trying to handle this automatically, and just write the serializer create and update methods exp…
I know why it's not supported and I agree that there should be a third party package for it that is more or less officially supported/recommended like the jwt package.
Most recently I created a new handler object that runs some introspection of the model. I then override my model view sets' create and update methods to implement the handler. Maybe I should get off my ass and open source it (currently buried in a project).