Vitaliy Kucheryaviy

I'm not sure about this one... my thoughts is actually returning tuples with included status was originally not best design idea I'm actually leaning into some check that forces user...

Hi @JimNero009 I guess the simpliest would be to extend Router and override it: ```Python from ninja import Router class RouterWithDecorator(Router): def __init__(self, decorator, **kwargs): self.decorator = decorator super().__init__(**kwargs) def...

Hi @davidszotten thank for PR I was thinking about a bit different approach for request param basically now django-ninja supports any django views decorator (with decorate_view helper) and Django's "protocol"...

or even simpler - just drop first parameter entirely

hi @jlucas91 basically the problem is that each operation(path) has is it's own url-name - and if you include it twice it will have a clashing naming Indeed this is...

Hi @sumebrius could you show on pydantic doc where they require this ? Generally it works, but just not very type-accurate

@jmriebold did you try returning non validated objects ( I did not investigate this deeply - but most likely it just does double validation) try this ```Python @api.get('/examples', response=ExampleListSchema, by_alias=True)...

@samuelchen could you show definition for - `ApiRespCode.SUCCESS` - `Promise` - code for `def ApiResults.SUCCESS`

@kingychiu there are no mechanics to pass context yet from view function... maybe something like could work in future: ```Python @api.get("/some", response=SchemaWithContext) def some(request...) return WithContext({"some": "data"}, context={"some": "context"}) ```...

@kingychiu the `WithContext` can be just a special django-ninja wrapper that will just notify renderer to include passed context to a desired response