[Feature] Add support of nested URLs

[imapanda]

Is this feature missing in the latest version?

• I'm using the latest release

Is your feature request related to a problem? Please describe.

It looks impossible to handle nested URLs like this :
/libraries/1/books/1/

What would work currently is if we separate urls into :
/libraries/1/
and
/books/1/

Describe the solution you'd like?

I tried to play with the function list_view_url inside generic.list.py and found out that reverse(self.__list_view_name,kwargs=self.kwargs) would kind of work but breaks others things.
It would be a good start to continue playing with this but i'm too new to this repo to help anyone.

Maybe someone understands my problem ! I'll be happy to provide more help/infos if needed :)

Kind regards

Describe alternatives you've considered?

No response

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience.

[vanderzielj]

I just started playing with django-view-breadcrumbs a couple of hours ago so I am glad I stumbled onto this; I need to be able to do the same. In fact I would like the breadcrumb to go arbitrarily deep something like this:
/org/2/asset/5/system/4/component/12

[nicokant]

Hi, my workaround to this is to use BaseBreadcrumbMixin directly in each View and to implement for each a crumbs cached_property that resolves the urls correctly.
You won't get the benefits of DetailBreadcrumbMixin, etc.. but you'll have full control of the nesting.
Here is my solution: NINAnor/genlab_bestilling@a9c2582

NOTE: I didn't want to migrate to a namespace for model name resolution or to change all my path names