T. Franzel

Hi, this was discussed before in #375 please see this: https://github.com/tfranzel/drf-spectacular/issues/375#issuecomment-1255634229 and https://github.com/tfranzel/drf-spectacular/issues/375#issuecomment-1373537264 for a solution. You basically need an `OpenApiSerializerExtension` and you also need to give each variation an...

Hi @vabene1111, interesting! So you are saying `drf-writable-nested` serializers behave differently depending on their location inside the payload (root vs nested). That is indeed not covered by spectacular, as we...

> The problem is the loss of context. On the root view the ID comes from the ID parameter of ... Yes, I got that. I was merely stating it...

I would recommend this: * define a custom model field `class BCharField(models.CharField): pass` and use it instead. * write your `BSerializerField(serializers.CharField)` * patch the mapping into the root class: `ModelSerializer.serializer_field_mapping[BCharField]...

Hi, > But trying to access api/v1/schema throws Object of type 'str' is not JSON serializable error and the str references to migration files upon searching in the codebase. where...

~~The type hint does not reflect that because `list[..]` **was** not supported there.~~ ~~We reflected on that deliberate choice and reversed it. `list` and other higher order hints were added...

Scratch what I said, it was wrong. The feature I was referring to is basically the same thing, but applies somewhere else (not`@extend_schema_field`). Shouldn't answer issues that late 😄 Okay...

Added a fix to fully support regular as well as higher order types (union, dict, list). The hint now also includes basic types (str, int, ...). Unfortunately, it is tricky...

yes it should reload. not exactly sure why. I have only tested this for non-oauth cases myself. * is there something in the browser console? warnings? * has this ever...

Excellent! Of course they used another method. doh. Do you want to make a PR or should I add it when I come around to it?