Conversation
|
Review requested:
|
Renegade334
left a comment
There was a problem hiding this comment.
I feel like this is probably reasonable, given that we already allow non-Uint8Array array buffer views. There are certain API surfaces that return raw ArrayBuffers (thinking webcrypto in particular), the required change is a one-liner, and there's already asymmetry in terms of the type conversion for BLOBs.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #62061 +/- ##
==========================================
- Coverage 89.74% 89.64% -0.11%
==========================================
Files 674 676 +2
Lines 204883 206242 +1359
Branches 39379 39506 +127
==========================================
+ Hits 183882 184889 +1007
- Misses 13279 13467 +188
- Partials 7722 7886 +164
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
The following line also needs to be updated, so that array buffers aren't treated as named parameter binding objects:
Line 2164 in 1f2afe9
There was a problem hiding this comment.
It would be better if you tested this behaviour by adding to test/parallel/test-sqlite-typed-array-and-data-view.js instead (you can also add cases for both ArrayBuffer and SharedArrayBuffer).
This also has the benefit of passing array buffers in the first binding argument, which tests the object binding behaviour mentioned above.
Fixes: #61396