Skip to content

when converting nulls, do not change the original data - #125

Merged
uw4 merged 1 commit into
mainfrom
124-utilsconvertnulls-mutates-its-input-so-a-nested-evaluate-in-a-custom-function-corrupts-json-nulls-in-the-outer-expression
Nov 4, 2026
Merged

uw4 merged 1 commit into
mainfrom
124-utilsconvertnulls-mutates-its-input-so-a-nested-evaluate-in-a-custom-function-corrupts-json-nulls-in-the-outer-expression

Conversation

@aeberhart

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

Test Results

1 798 tests  +2   1 795 ✅ +2   7s ⏱️ -1s
  120 suites ±0       3 💤 ±0 
  120 files   ±0       0 ❌ ±0 

Results for commit 0a71986. ± Comparison against base commit 7dd27a5.

@uw4
uw4 merged commit a436ed4 into main Nov 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Utils.convertNulls mutates its input, so a nested evaluate in a custom function corrupts JSON nulls in the outer expression

2 participants