Vitaliy Kucheryaviy

yeah, I would say either it should allow it in get or it should make schema docs for request body OR it should validate - that user must not declare...

@limugob @fantasticle @bencleary Well.. django-ninja uses django url resolver under the hood, which does not allow to set more than one name to url so whenever you use THE SAME...

@limugob > because in django it is possible to give the same url two separate names. no, as I see it's there is only one `name` string argument for `path`...

@sunboy123 @martinlombana @alirezapla > if more than one foreignkey? i feel this solution is not very well. I guess the easiest solution for now is to manually write ids in...

Hi @frossigneux just tried your solution, but stuck at making a socket: ``` pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket Connection failure: Connection refused pa_context_connect() failed: Connection refused ``` any idea ?

> Do you have any predictions on when this will be merged? @vitalik well I'm still thinking about it - as some times I see people have this error, but...

Hi @flaeppe I'm still considering adding this... but too much conflict at the momment would you be able to create a new PR from v1

> Are there any plans to tackle this? @rkulinski the `resolve_` seems working good here ? what's your vision ? maybe this also can work ```Python class User(models.Model): email =...

Hi @lucasrcezimbra Query params do not have a "standard" way to pass structured data, but since all query params are atumatically flattened by django ninja you can achive it like...

@lucasrcezimbra not sure if this is what you need: ```Python class PostSchema(Schema): id: int = Field(None, alias="post__id") title: str = Field(None, alias="post__title") class UserSchema(Schema): id: int = None username: str...