How to bulk update/insert via nested url?

[simkimsia]

Using the nameserver and domain example, I like to send a list of domains to the nested route

/nameservers/{nameserver-pk}/domains

and then I can write code to decide to which domain is supposed to be a brand new record or which domain is supposed to update.

How do I do that using nested-routers?

I am okay to write my own code, I am not sure how to use the right viewset and serializer for this.

[himanshu-singh1995]

As you are using drf-nested-router, I assume you want to adhere to the rest architecture.

Using the nameserver and domain example, I like to send a list of domains to the nested route

/nameservers/{nameserver-pk}/domains

Doing so is not recommended by REST architecture. As REST architecture provide CRUD operations(
get on /nameservers/{nameserver-pk}/domains gives list of domains of the nameserver
post on /nameservers/{nameserver-pk}/domains add a domain to nameserver
) but here you tring to add a custom operation. So REST recommends
POST request on /nameservers/{nameserver-pk}/domains/bulk-create (not exactly bulk-create, you can have here whatever you want) for bulk create.

This can be easily achived by adding a list_route with path='bulk-create, methods=[post]' in DomainViewSet

[GregEremeev]

Doing so is not recommended by REST architecture.
So REST recommends
POST request on /nameservers/{nameserver-pk}/domains/bulk-create

@himanshu-singh1995 Can you provide a link to clarify that comment? Where did you get that?

[alanjds]

Well, this is very debatable @himanshu-singh1995. Some would say that using nested objects is not RESTful just to start.

My position is that a POST with a list on the {}/domains/ is preferred than a POST with a list on {}/domains/bulk-create subpath.

@simkimsia I would answer as if every member of the list had been POSTed alone. On the view, you can differentiate by verifying if the request cames with a dict or a list on the 1st level, for example.

However, is just an opinion.