T. Franzel

this is an interesting ask and does indeed make sense. however changing this may break a lot of users. when we also source from the parameters, it impacts the global...

the fix should be easy. problem is that this breaks everybody using `get_name` in an extension. i failed to include a `**kwargs` in the beginning so that its forward compatible....

awesome! i'll leave this open to gather some support from other users. if this becomes a more common pain point we can look at it again. in the meantime i...

so I just hit this problem without a proper way to achieve the goal. `Direction` was indeed needed. I found a way to safely call legacy `get_name` without the new...

Hi @mdefeche I tested the https://github.com/alanjds/drf-nested-routers#infinite-depth-nesting example and it looks ok to me. We don't have special handling for 2 levels and so 3 levels shouldn't be any different from...

glad you managed to get a solution. i had a look but the issue was involved and i was unable to come up with a good suggestion without investing too...

the view schemas are accessible through `result`. that much you know. the serializer is accessible through the registry. you can access it with `generator.registry`. there you have all the `ResolvedComponents`...

there is no concept for choice labels in OpenAPI. the only thing one could do is generating a description that contains all the choice label tuples. certainly an option.

ahh i see. thanks for the research. we could hack together a description string but i would prefer not to. regarding the solutions in OAI/OpenAPI-Specification#681: we should wait until some...

That looks promising. However, not much use implementing it until at least `swagger-ui` and `openapi-codegen` follow suit.