chore: test update - added array type to error arguments

Author: JeneaVranceanu

Tests/web3swiftTests/localTests/ABIElementsTests.swift

@@ -26,6 +26,7 @@ class ABIElementsTest: XCTestCase {
         XCTAssertEqual(EthError(name: "Error", inputs: [.init(name: "           ", type: .address)]).errorDeclaration, "Error(address)")
         XCTAssertEqual(EthError(name: "Error", inputs: [.init(name: "           ", type: .address), .init(name: "", type: .uint(bits: 256))]).errorDeclaration, "Error(address,uint256)")
         XCTAssertEqual(EthError(name: "Error", inputs: [.init(name: "sender", type: .address), .init(name: "    ", type: .uint(bits: 256))]).errorDeclaration, "Error(address sender,uint256)")
+        // Not all types are supported in errors, e.g. tuples and functions are not supported
         let allTypesNamedAndNot: [ABI.Element.InOut] = [
             .init(name: "sender", type: .address),
             .init(name: "", type: .address),
@@ -44,11 +45,12 @@ class ABIElementsTest: XCTestCase {
             .init(name: "someFlag", type: .bool),
             .init(name: "rand_bytes", type: .bytes(length: 123)),
             .init(name: "", type: .dynamicBytes),
+            .init(name: "arrarrarray123", type: .array(type: .bool, length: 0)),
             .init(name: "error_message_maybe", type: .string),
         ]
         XCTAssertEqual(EthError(name: "VeryCustomErrorName",
                                 inputs: allTypesNamedAndNot).errorDeclaration,
-                       "VeryCustomErrorName(address sender,address,uint8,uint16,uint32,uint64,uint128,uint256,int8 my_int_8,int16 my_int_16,int32 my_int_32,int64 my_int_64,int128 my_int_128,int256 my_int_256,bool someFlag,bytes123 rand_bytes,bytes,string error_message_maybe)")
+                       "VeryCustomErrorName(address sender,address,uint8,uint16,uint32,uint64,uint128,uint256,int8 my_int_8,int16 my_int_16,int32 my_int_32,int64 my_int_64,int128 my_int_128,int256 my_int_256,bool someFlag,bytes123 rand_bytes,bytes,bool[] arrarrarray123,string error_message_maybe)")
     }
 
 }