Skip to content

fix(jni): check integer ranges at binding boundaries - #1099

Merged
andiwand merged 1 commit into
mainfrom
review/81-jni-integer-bounds
Oct 5, 2026
Merged

andiwand merged 1 commit into
mainfrom
review/81-jni-integer-bounds

Conversation

@andiwand

@andiwand andiwand commented Oct 5, 2026 •

Copy link
Copy Markdown
Member

🤖 Generated with Claude Code

JNI now checks integer ranges when converting rendering limits, spreadsheet coordinates/counts, color channels, CSV delimiters and table positions. Negative Java values no longer become huge unsigned limits, and values outside Java's signed range no longer return wrapped coordinates. A shared conversion helper keeps those checks consistent.

Validation: all 81 JNI tests pass. Three targeted checks fail on the parent revision. Existing style, delimiter and position tests cover further boundaries; two new tests cover configuration and sheet inputs. Clang-tidy still reports existing public-header diagnostics and an existing redundant move in wrap_element.

@andiwand
andiwand force-pushed the review/80-jni-unicode branch from 4f8c6ab to a77a232 Compare October 5, 2026 20:30
Base automatically changed from review/80-jni-unicode to main October 5, 2026 20:32
@andiwand
andiwand force-pushed the review/81-jni-integer-bounds branch from 308873c to afc3a6e Compare October 5, 2026 20:32
@andiwand
andiwand merged commit 18b3323 into main Oct 5, 2026
23 checks passed
@andiwand
andiwand deleted the review/81-jni-integer-bounds branch October 5, 2026 20:33
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.

1 participant