Django REST framework 3.1 released
django-rest-framework.org
Django REST framework 3.1 released
1–10 of 46 posts
Re: Django REST framework 3.1 released
#2Still no M2M for ModelSerializer..? Guess I'll have to just keep using a ton of shitty hacks.
Re: Django REST framework 3.1 released
#3Still no M2M for ModelSerializer..? Guess I'll have to just keep using a ton of shitty hacks.
Of course you can use many to many fields with ModelSerializer.
I'm not sure what you mean here, but I'd suggest opening an issue if you believe there's a problem - we're pretty comprehensive about dealing with incoming issues.
Re: Django REST framework 3.1 released
#4Just wanted to say that this is one of the most beautifully-documented projects I've ever used. Bravo!
Re: Django REST framework 3.1 released
#5@OP:
What is your long term vision for the project?
Reason I ask is due to how django keeps (IMO) gaining territory on the corporate and/or business stack. I get requests for support and new development consistently from companies in different markets/regions.
Re: Django REST framework 3.1 released
#6Is the upgrade path from django 1.4.18 / drf 2.4.2 relatively easy?
Re: Django REST framework 3.1 released
#7[deleted]
Re: Django REST framework 3.1 released
#8@OP: What is your long term vision for the project? Reason I ask is due to how django keeps (IMO) gaining territory on the corporate and/or business stack. I get requests for support and new development consistently from companies in different markets/regions.
Broadly, we aiming for it to be a mature, sustainable and well-supported general purpose Web API framework.
We tend to be fairly aggressive about keeping the scope manageable in order to keep to that. For example 3.1 moves some functionality out into third party packages, so that we can concentrate on the quality of the core framework.
Some of the longer term feature work:
* Admin style interface - See https://www.kickstarter.com/projects/tomchristie/django-rest...
* Fuller support for alternative storage backends. Eg. Easier to integrate with SQLAlchemy, as an alternative to the Django ORM.
* Hypermedia support & client library. (Too involved to go into detail here.)
Re: Django REST framework 3.1 released
#9Is the upgrade path from django 1.4.18 / drf 2.4.2 relatively easy?
The 3.0 release notes are the place to start for looking at upgrading. They go into quite a bit of detail about this.
Re: Django REST framework 3.1 released
#10Just wanted to say that this is one of the most beautifully-documented projects I've ever used. Bravo!
Agreed, although I wish there was more documentation on the benefits of each feature, rather than just how to implement it.
E.g. there are dozens of pages on how to implement serializers, which is great, but the section on the benefits of serializers is only a paragraph or two long. So after reading all the documentation I'm still unclear as to the best practices on when vs when not to use them, and what the best practices are for endpoints that don't take advantage of them. I'm sure this kind of stuff is obvious to people who have been using it for a while, but after just going through the tutorial and then reading the relevant API pages I was still unclear on a bunch of issues.