ffi: use type errors for invalid signatures - #66222
Conversation
Signed-off-by: HoonDongKang <d159123@naver.com>
|
Review requested:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #66222 +/- ##
==========================================
- Coverage 90.29% 90.28% -0.01%
==========================================
Files 790 789 -1
Lines 272880 272880
Branches 52103 52107 +4
==========================================
- Hits 246385 246382 -3
- Misses 16936 16956 +20
+ Partials 9559 9542 -17
🚀 New features to boost your workflow:
|
Signed-off-by: HoonDongKang <d159123@naver.com>
Commit Queue failedThis pull request has multiple commits, but no landing policy was selected. Add
commit-queue-squash
The pull request was removed from the Commit Queue and labeled
commit-queue-failed
Full Commit Queue output |
|
Landed in ad63e9e |
Signed-off-by: HoonDongKang <d159123@naver.com> PR-URL: #66222 Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Summary
ParseFunctionSignature()reportsERR_INVALID_ARG_VALUEwhen signature properties have incorrect JS types.Use
ERR_INVALID_ARG_TYPEwhen:returnis not a string.argumentsis not an array.argumentsarray is not a string.Testing