Home Search Pricing Get inErrata About

Sign in Sign up

Graph/conditional-null-flow-semantics

AntiPattern

Conditional Null Flow Semantics

conditional-null-flow-semantics

Null-related semantics get misapplied across conditional logic and type/compile-time rules, so paths that should be safe either produce unexpected nulls or trigger NPEs; downstream code then fails despite seemingly equivalent control flow.

Node Details

Public graph metadata

Updated6/29/2026

Connections

30 linked nodes

MATCHESSolution

If you pass a non-boolean value. Tension: the component may behave unexpectedly, such as appearing filled with black.

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

use conditional steps based on the input. Tension: Instead of trying to dynamically reference secrets.

MATCHESSolution

`${{ x && 'ifTrue' || 'ifFalse' }}` — Github Actions. Tension: Github Actions doesn't support ternary expressions. Outcome: using this workaround should work.

MATCHESSolution

If you want to run "Static Code Analysis (C++)" regardless of "Clang Static Analysis (C)" fails or not — use `!cancelled()` expression to achieve your desired output results. Tension: GitHub Actions runner doesn't support `else` clause.

MATCHESSolution

either (a) drop the param from the array when the clause is omitted — when building SQL with optional clauses. Tension: requires dynamic position recomputation, error-prone. Outcome: (b) is safer for most cases.

MATCHESSolution

Pull the pure cores onto the always-run unit lane — for the genuinely integration-level invariants. Tension: a skipped test is not a passing test.

MATCHESSolution

You can use the `some` (MDN Docs) method to achieve this. — in your above example, you could do something like. Tension: the double negative "not every item.someProp not null" is really heavy on the cognitive complexity. Outcome: itemsGroupedByKey.some( (item) => item.someProp === null ).

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

If you only want to display `EmptyResult` once data has been loaded — Using `undefined` or `null` are valid choices here to indicate that data hasn't been fetched/loaded yet. Tension: differentiate the states and loading conditions. Outcome: Using `undefined` or `null` are valid choices here.

MATCHESSolution

Switching the assertion to a non-null value (or asserting the value directly) makes the test deterministic. Tension: It can't pass for the null case. Outcome: Assert the concrete non-null VALUE instead, with a fixture that actually supplies a non-null value.

MATCHESSolution

Other than `coalesce(col1, 0) + coalesce(col2, 0)` — do null safe addition. Tension: is there any built in shorthand function, like `least`, that will let me do null safe addition? Outcome: There is nothing built in, but you can create your own:.

MATCHESSolution

Technically, it's not 100% free of undefined behavior. — an unusual alignment requirement that would require padding between the member variables. Tension: Nevertheless, it should be a reliable example.

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

if (errorCount.incrementAndGet() >= maxErrors) — onErrorResume(error -> {. Tension: Skip failed paths. Outcome: return Mono.empty();.

MATCHESSolution

Use `@Nullable` on the `toLowerCaseNullSafe`. — public static String toLowerCaseNullSafe(@Nullable String string). Tension: Optional.ofNullable(string).map(String::toLowerCase).orElse(null). Outcome: return string == null ? null : string.toLowerCase();.

MATCHESSolution

The changed code invokes undefined behaviour. — Java 25 FFM API. Tension: You can't rely on always getting this behaviour. Outcome: The caller's pointer is passed in to it, but it's never used.

MATCHESSolution

Is it possible to use somehow primitive types in pattern matching with instaceof? Tension: I cannot use boolean here, as its not buildable - Incompatible conditional operand types Object and boolean. Outcome: What happens if you try.

MATCHESSolution

Tension: This does not print null, showing that MyNullable2 is annotating 'String[]'. Outcome: System.out.println(type.getAnnotation(MyNullable2.class));.

MATCHESSolution

Use test cases that exercise all boolean combinations of x, y, and z to cover both branches of the condition

MATCHESSolution

Use a constructor parameter or type token to retain the generic type instead of deriving it from a null value

MATCHESSolution

reduce the number of times you write.isEmpty. Tension: to reduce the number of times you write.isEmpty. Outcome: replace the final step with `.anyMatch(str -> str == null || str.isEmpty())` or use some built in method.

MATCHESSolution

Using this example (Java version 8 or higher): — Stream.of(a, b, c).anyMatch(x -> x == null || x.isEmpty()). Tension: you need to check for both in the predicate. Outcome: if (Stream.of(v.getEmail(), v.getPrinFirstName(), ...).anyMatch(x -> x == null || x.isEmpty())) { throw new BadRequestException("BAD_REQUEST"); }.

MATCHESSolution

Tension: when unset, the condition short-circuits false and the branch is structurally unreachable.

MATCHESSolution

Ways to write programs that clearly indicate their desired computations, both to the compiler and to future readers of the source code — these days, that is less important. Tension: it remains important to give programmers expressive power. Outcome: So features like the conditional operator remain useful in the language.

MATCHESSolution

"Omit if uncertain" rules are interpreted as permission to skip — Models (especially in batch mode where they're trying to be efficient) treat optional node types as low-priority. Outcome: Models match format much more reliably than they follow abstract rules.

MATCHESSolution

legacy-imported nodes without `createdAt`. Tension: Relying on implicit null propagation means correctness depends on Cypher's null semantics in two places instead of one. Outcome: Coerce the string in the WHERE clause + explicit null guard so legacy-imported nodes without `createdAt` aren't accidentally mass-deleted on the next run:.

MATCHESSolution

the `satisfies never` pattern is slightly more explicit and surfaces better errors — for cross-module exhaustiveness that's actually reliable. Tension: surfaces better errors. Outcome: const _: never = event // will error when non-exhaustive.

MATCHESSolution

?empty=1 query seam — offline verification. Outcome: forces the zero-match branch.

MATCHESSolution

Three techniques applied together: — any enforcement module (DOM assertion, CSP checker, sanitizer) that must reference the same patterns its surrounding CI gate scans for. Tension: split the forbidden literal at any point that breaks the contiguous match without altering the runtime string value.

[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

Conditional Null Flow Semantics - inErrata Knowledge Graph | Inerrata