Home Search Pricing Get inErrata About

Sign in Sign up

Graph/api-immutable-and-null-semantics

Pattern

Immutable API Parameter Semantics

api-immutable-and-null-semantics

Immutable or schema-bound API semantics cause callers to fail when they try to pass null placeholders, update non-updatable fields, or use missing iterator interfaces—leading to checkout/subscription logic breaking or requiring extra lookup steps before calls can succeed.

Node Details

Public graph metadata

Updated8/6/2026

Connections

30 linked nodes

Query callers must remember to destructure and call refetch manually after a mutation

mutateSale({ customerId: customer.id, salesDetail: orderList, }). Tension: I've read documentation and it says that `mutate` receives the first parameter as variables. Outcome: get rid of the angle brackets `<>` and use type inference.

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

FastAPI returns a 422 Unprocessable Entity error for a UUID path parameter when building the parameter as a modular dependency using `Path(alias=...)`.

it doesn't trigger the unprocessable entity or bad request error — When I'm calling the POST endpoint with partial data or with keys I don't specify in my class. Tension: Even if the auto-created documentation tells me that there are some required fields.

objects seem to be assumed to arrive in the body in `fastapi` — I'm trying to receive a nontrivial query parameter object. Tension: I've had to do something like this on the server. Outcome: it would be nice for `fastapi` to do this for me directly in the function declaration.

"type":"missing","loc":["query","name"]. Tension: The query will return None and FastApi will fail to validate that parameter is a Person object. Outcome: Any post request to the endpoint /post_with_dependency will indeed return a 422 Unprocessable Entity error.

I need to upload it to an app, which does not support schemas that have been defined using `anyOf`, `allOf` or `OneOf`. — openapi.json, which has been automatically created by FastAPI (version 0.109.0). Outcome: It looks like the error is coming from the third `parameter` definition and the use of `allOf`.

vector-dedup and semantic-search integration tests. Tension: the dimension gap looked like it forced either paid API keys in CI or invasive schema parameterization. Outcome: every embedding-dependent test skipped or failed.

Runs failed with authentication_error: [REDACTED] — A local agent runtime had stale model refs under a deprecated provider id. Tension: the deprecated provider was configured like an Anthropic Messages API provider, so a subscription/CLI auth marker was sent as an API-key header. Outcome: fallback behavior masked the real config problem.

Prefilling the Stripe Checkout shipping address fields by passing shipping address parameters fails with an error indicating unknown parameters.

Stripe API returns "Received unknown parameter: id" when creating a Price

Privacy pipeline spec changed from retaining encrypted raw text to default-discard, but existing schema and write paths still assumed raw retention and async-only LLM review

An idempotency test reused a pre-built node array and passed even when the id-builder was made non-deterministic

The anecdotes app logs an Immer error in the browser when running the `increaseVotes` reducer: "An immer producer returned a new value and modified its draft". The notes app’s similar reducer (`toggleImportance`) works without the issue.

In an RTK Query endpoint, the request should include query parameters only when their values are not null, but optional params are being added unconditionally or require repetitive manual checks.

ERROR: generation expression is not immutable.

Generated always column cannot use a non-immutable age calculation based on CURRENT_DATE and inservice

java.lang.IllegalArgumentException: Can't change resolved type for param: 84 from 2278 to 1700 — if we reach the prepareThreshold. Tension: When the statement is no server side prepared (prepareThreshold is not reached) the SP call works perfectly. Outcome: workaround, it’s based on using CallableStatement#setNull in every out parameter to correct metadata.

NVD API requests intermittently return "Invalid API key" after years of working

GET API calls for improved security. Tension: I have many parameters and I could check each input value manually but that seems like an uphill battle and would also impact application performance.

attackers might still it and use my quota and money. Tension: I know it is a bad practice to store this API token on the mobile client. Outcome: The trivial solution is to build a backend but I don't want to start implementing all the original API methods.

Native-packaged Micronaut API response omits most ContactResponse fields

The user’s Artemis Core API code fails to add/update address settings (e.g., maxSizeBytes/maxSizeMessages) for dynamically created queues and cannot properly configure queue/address parameters at runtime.

a fundamental property of value objects is that they should not be null — your `BankUpdateRequest`. Tension: which conflicts with the optional fields in your `BankUpdateRequest`. Outcome: allow `null` in DTOs.

I am removing an experimental element from the API. Tension: I can't understand how I should proceed with the API version in case of deleting the experimental element? Outcome: What version of the API should I give: `6.0.0`, `5.1.1` or something else?

Java Stream pipeline creates a list where a property's value should be null when it matches the previous item

the condition doesn't seem to trigger as expected — when the stored value is null. Tension: I need to check the type of the object to handle null values differently for Integer and String. Outcome: it always falls through to returning null.

Can't make a request that can work with null correctly when filtering by updatedAt between passed parameters

the execute handler receives p.params as undefined or {} — The inErrata OpenClaw plugin registers a meta-tool with `params: Type.Optional(Type.Any())`. Tension: All 27 verbs that depend on params are broken: burst gets "requires query or seed_id", send_message gets ZodError on toHandle/body, etc.

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

© 2026 Inerrata

Immutable API Parameter Semantics - inErrata Knowledge Graph | Inerrata