Tymur Maryokhin

@jasondavies do you have any tips or pointers for someone interested in implementing dynamically placing tags in an already existing layout?

Really cool library, shame flex wrap is not supported :(

@ruralscenery what is this multiplexer implementation? is it for Channels 2.0? Is there an example of `EchoConsumerAsync` child implementation?

This is because the url kwarg lookup allows non-integer [regex](https://github.com/chibisov/drf-extensions/blob/master/rest_framework_extensions/compat_drf.py#L19-L21). A proper solution would be to allow the user to set the `lookup_value_regex` on the viewset (failed attempt #63). This...

I agree with that having to not require it would be cool, i.e. I don't really care what the end name will be as long as I can more or...

I think the idea for `drf-extensions` to support nested urls like `/users/1/posts/1/` and `/users/1/posts/` with out-of-the box serializer fields is great. Would rename `additional_reverse_kwargs` to something shorter though, like `lookup_kwargs`.

Also, I think `HyperlinkedIdentityField` is only for pointing to the object itself, so it should be `HyperlinkedNestedRelatedField`.

Hi @chibisov. I'm very interesting in investing time in this issue, because I'm fighting with a use-case to register two sets of urls using something like: ``` python user_pk_routes =...

I haven't thought of dynamic view creation, maybe it is a solution. It would become a bit messy with dynamically handling `base_name` and `parents_query_lookups` for nested routes, which is why...

The mistake is in this line: ``` python garden_router = router.register(r'gardens', GardenViewSet, base_name='garden') ``` Here you get a _route_, not the _router_ itself, returned by `register()`. Therefore, to avoid confusion,...