You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API interface, at least in all test files, looks really strange to me, as I'm expecting JSON string as input (and the outputs are normally JSON string as well). However, all test cases covered are just using a series of integers as input, which is quite unusual.
Would it be possible that you extend the test coverage to normal JSON strings as well? For e.g., you can use the following operation, input and output. Thanks.
The API interface, at least in all test files, looks really strange to me, as I'm expecting JSON string as input (and the outputs are normally JSON string as well). However, all test cases covered are just using a series of integers as input, which is quite unusual.
Would it be possible that you extend the test coverage to normal JSON strings as well? For e.g., you can use the following
operation
,input
andoutput
. Thanks.The text was updated successfully, but these errors were encountered: