Hacker News Reader

Comment by sandGorgon | Hacker News Reader

my only blocker for migrating a legacy application to DRF is because it doesnt have support for nested routes (and I have to use a third party package).

AFAIK this is deliberate and opinionated.

View on HN

What do you mean by nested routes? You can definitely have an API which looks like this: /api/people/morgante/comments/3000/

You can also use the include(x.urls) feature to really simulate nested routes.

http://www.django-rest-framework.org/api-guide/routers/#drf-...

See for yourself.

I'm not sure why that would prevent you from migrating to DRF. It's clearly supported and there's even a helper module to nested routes even easier.

I'm not really sure why a framework would take a position where something is important (and probably requested enough) to put it in the official documentation.... but not make it part of the core.

I fear we-barely-tolerate-it syndrome.

It's entirely possible to do in core without any extensions. It seems like you're just coming up with ridiculous excuses to not use DRF.

I'm willing to learn. I don't understand why you term it as "ridiculous", when the official documentation points to an external package.

Is the documentation wrong ? If there's another way...why does it not get mention there?

From my perspective, this is weird.

First of all, why can't you use an external package?

If all you want is URLs which look like "/api/people/morgante/comments/3000/" it's easy enough to construct those simply as standard viewsets. They're totally normal.

I've used https://github.com/alanjds/drf-nested-routers with success.

Reply on news.ycombinator.com