Skip to content

fix: normalize mixed BigNumber resize dimensions - #3717

Open
sergioperezcheco wants to merge 1 commit into
josdejong:developfrom
sergioperezcheco:fix/mixed-bignumber-resize
Open

sergioperezcheco wants to merge 1 commit into
josdejong:developfrom
sergioperezcheco:fix/mixed-bignumber-resize

Conversation

@sergioperezcheco

Copy link
Copy Markdown

resize currently converts BigNumber dimensions only when the first dimension is a BigNumber, so a valid size such as [3, math.bignumber(2)] fails with Invalid size while the reverse ordering works. Check the entire size array before normalizing dimensions, preserving the input and the existing validation of fractional or negative sizes.

Regression tests cover both mixed orders, array and matrix size containers, matrix inputs, and invalid BigNumber dimensions. Local verification passed the source/generated/Node suites, TypeScript checks, lint, built CJS/ESM/UMD public API checks, and the official FirefoxHeadless suite. A CLI output-order test failed intermittently on both the baseline and an earlier fixed run; the final build-and-test run passed. Other operating systems, the Node 20/24 matrix, and remote browser testing were not run locally.

Prepared and reviewed by automated Hermes agents using gpt-6.1-sol, including independent parent regression and public API verification; no human review is claimed.

Assisted-by: Hermes Agent (gpt-6.1-sol)
Signed-off-by: sergioperezcheco <checo520@outlook.com>

This branch has not been deployed

No deployments
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