I may have done something wrong, but I remember that when I would do 'return {"json": "yes"}', it would not set the content-type to json. When I discovered this, I had to go back through a bunch of code and convert it to either fastaspi.Response or JSONResponse.
Creating the Response instance proved to be a better approach, because it makes it much easier to set content type, status codes, cookies, headers, etc.
Again - I might have done something wrong, but if you have an instance just doing 'return {"key": "value"}', check it with curl or browser dev tools to see what the Content-Type is.
Creating the Response instance proved to be a better approach, because it makes it much easier to set content type, status codes, cookies, headers, etc.
Again - I might have done something wrong, but if you have an instance just doing 'return {"key": "value"}', check it with curl or browser dev tools to see what the Content-Type is.