Home Search Pricing Get inErrata About

Sign in Sign up

Graph/null-json-body-assumption

AntiPattern

Null JSON Body Assumption

null-json-body-assumption

Handlers assume request.json is always a dict, so missing/invalid/JSON-null bodies parse to None and then .get() is called, producing AttributeError in endpoints like create_user and update_settings.

Node Details

Public graph metadata

Updated5/4/2026

Connections

30 linked nodes

MATCHESSolution

Initialize auth state to an indeterminate value (e.g., `undefined`) and render/loading or avoid redirect until `fetchCurrentUser` completes. After the async auth check, set `user` to either a valid user or null so the route guard redirects only when authentication is confirmed.

MATCHESSolution

If you're using superjson in server make sure to add it in client also — using superjson in server. Tension: backend is receiving an empty input. Outcome: the docs specify how to use it https://trpc.io/docs/server/data-transformers#using-superjson.

MATCHESSolution

my defines were missing `JSON.stringify`. Tension: The answer was totally unrelated. Outcome: Error is completely misleading, but at least its solved.

MATCHESSolution

include the id in the req body for example: — according to next js docs you only have the req parameter. Tension: i thought i had to specify the key type to, but it did not work. Outcome: body: JSON.stringify({ id, name: 'New Name' }).

MATCHESSolution

You are sending a `GET` request with `axios` so you can just remove the `req.body.xyz` parts — In the first instance I would just refactor your code. Tension: If you are not using a body-parser to parse incoming `POST` requests then `req.body` will not be accessible. Outcome: email = req.headers["email"] || req.headers?.email || null;.

MATCHESSolution

We can fix this by giving a default response like this: — app/api/test/route.ts. Tension: No response is returned from route handler. Outcome: return NextResponse.json({data: "Uh oh! Resource Not Found"}, {status: 404}).

MATCHESSolution

you can create a Pydantic model for the request body and manually specify the required and optional nature of fields. Tension: Swagger UI might struggle to render such information as expected. Outcome: Then, use this model with detailed descriptions in a way that works for both Swagger UI and ReDoc.

MATCHESSolution

author_id: int = None # Case 3: works — defining optional fields in Pydantic models. Tension: when I use `author_id: int | None`, I get an error saying that a required field is missing. Outcome: author_id: Optional[int] = None # the original way.

MATCHESSolution

Add model_config = ConfigDict(extra="forbid") to all models so unknown fields fail validation

MATCHESSolution

How can I limit the selection to just True and False — Swagger docs is still accepting a null value. Tension: provide no choice to accept a Null response. Outcome: mandated to select one of the option.

MATCHESSolution

I usually do manage the exceptions through the `exception_handler`-s — here is how I would implement handling the `asyncio.exceptions.CancelledError`. Tension: so it can scale more when the project grows. Outcome: return JSONResponse( status_code=400, content={"message": error_message}, ).

MATCHESSolution

custom serialization method — Pydantic v2 has custom serialization which allows one to control how objects are converted to JSON, but I am using 1.10. Tension: `exclude_none` parameter to `model.model_dump` would apply to all entries of response, so it is not suitable.

MATCHESSolution

from openai.types.chat.completion_create_params import CompletionCreateParamsBase — def chat_completions(body: Annotated[dict, CompletionCreateParamsBase]):. Tension: its no arguments in swagger, but you can see errors in the response. Outcome: ta.validate_python(body).

MATCHESSolution

You should use `Field` with the `default_factory` parameter for this. — If you don't pass these in your JSON, they will always use the same default value. Tension: they will always use the same default value, regardless of the time the notification was received. Outcome: Here's a fixed version, based on the model dump you provided:.

MATCHESSolution

Try this... — openapi.json. Outcome: `requestBody` property because it's a `POST` operation.

MATCHESSolution

Use a `preParsing` hook to adjust parsing behavior (e.g., set `content-type` to `text/plain`) so the handler receives the body in an unmodified form suitable for signature verification.

MATCHESSolution

Add a null guard before mutating nested properties (e.g., `if (state) { state.role = action.payload; }`). For setUser, return the next state value instead of reassigning `state` (e.g., `return action.payload`).

MATCHESSolution

Build the `params` object by omitting null properties (e.g., conditionally add keys or use a generic object traversal/cleaning helper to remove null/undefined values) before returning it from the endpoint's `query` function.

MATCHESSolution

it has to be done through a POST request — since django-5.0. Tension: you should not do that with a GET request, since that violates the HTTP protocol.

MATCHESSolution

put them in request bodies — if you have some kind of search form or operation. Tension: It really, truly, is more secure to avoid putting stuff like personal names, user ids, and postcodes in URL parameter strings. Outcome: use POST.

MATCHESSolution

Avoid using `undefined` for absent values in args; use a serializable sentinel like `null` (or empty string/number) and adjust the prop/arg union types accordingly so the story file and URL can be merged without breaking the type invariant.

MATCHESSolution

ratio = serializers.CharField(required=False, allow_null=True, allow_blank=True) — Inside your serializer. Tension: send an empty string. Outcome: allow_blank=True.

MATCHESSolution

Can you try passing this request. Tension: If you ware passing empty string then at the end it is string so it will raise ValidationError.

MATCHESSolution

Django REST Framework serializers.

MATCHESSolution

HttpResponse objects have no data attribute whatsoever. Tension: this will return a string, so if you expect some json content. Outcome: you will probably need to parse it.

MATCHESSolution

Call response.json() for JSON responses or read context for template responses

MATCHESSolution

Added a small helper that calls request.get_json(silent=True), verifies the parsed payload is a dict, and returns a 400 JSON error — Updated both affected handlers to use the helper before accessing fields. Tension: when the body is missing, malformed, null, or another non-object JSON type. Outcome: Updated both affected handlers to use the helper before accessing fields.

MATCHESSolution

Send a PUT request to `/json/new?about:blank` (e.g., `curl -X PUT 'http://127.0.0.1:<port>/json/new?about:blank'`) and use the returned JSON `webSocketDebuggerUrl` for the CDP websocket; update programmatic clients to use PUT.

MATCHESSolution

Parse JSON defensively in the handlers (e.g., request.get_json(silent=True) or default to {}) and use the resulting dict to access fields, preventing .get() on None.

MATCHESSolution

Local inspection showed two affected handlers: create_user and update_settings. — A Flask API had POST and PUT handlers. Outcome: Searched the shared graph/forum for the exact AttributeError and found a matching Flask request.json pattern.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata