Comments (6)
Yes, it's a good option, it's in my backlog
from django-ninja.
Hey @begyy
what are you thoughts...
Do you need to set response class for each individual operation? @api.get("", response_class=ORJsonResponse)
or is it enough to set one global like api = NinjaAPI(..., json_renderer=UJSON)
- that will handle both deserialising input and serialising output ?
I do not see any case for myself where I would want one operation to have ujson or other one stdlib json lib
from django-ninja.
Hi @vitalik better it api = NinjaAPI(..., json_renderer=UJSON)
from django-ninja.
Hi @begyy
Please try latest version with support for response renderers
https://django-ninja.rest-framework.com/tutorial/response-renderers/
from django-ninja.
Hi @vitalik
ok
from django-ninja.
@vitalik good
from django-ninja.
Related Issues (20)
- ModelSchema resolve field cause validation errors HOT 1
- api doc for models.BigAutoField primary_key HOT 1
- Calculated fields are not visible in the schema HOT 2
- [BUG] Response generation dramatically slower when using aliases in Ninja v1/Pydantic v2 HOT 10
- Model Schema for pydantic class not for django model HOT 1
- [BUG] Issue migrating nested ModelSchema with Schema to ninja v1 HOT 6
- Handling duplicate schema names
- [BUG] Serious issue with `alias` in v1 (django-ninja) HOT 7
- [BUG] filter() does not behavior like document described HOT 1
- Change root_url for serving openapi.json behind a reverse proxy HOT 3
- [BUG] Unable to generate pydantic-core schema for <class 'function'>. HOT 1
- [BUG] When running the server using django-ninja's router, there is an issue of multiple objects with different types being received. HOT 2
- How to use swagger and redoc together? HOT 1
- Support for middleware HOT 5
- [BUG] pagination does not support async view HOT 1
- [BUG] reponse field becomes null if route specified reponse=MySchema HOT 2
- [BUG] GenericModel error " Input should be a valid dictionary or instance of xxx"" HOT 4
- Pydantic context in response HOT 4
- Model validation
- [BUG] fields_optional = "__all__" not working properly HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from django-ninja.