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
Since lockTransactionId is a reference to a transaction id, the respective types should be the same. Strictly speaking this is currently not the case, with hex being a subset of alphanumeric.
lockTransactionId
is defined as follows in the transaction schemas:core/packages/crypto/src/transactions/types/schemas.ts
Line 288 in 9800e34
core/packages/crypto/src/transactions/types/schemas.ts
Line 311 in 9800e34
Since
lockTransactionId
is a reference to a transaction id, the respective types should be the same. Strictly speaking this is currently not the case, withhex
being a subset ofalphanumeric
.core/packages/crypto/src/validation/schemas.ts
Lines 20 to 23 in 9800e34
lockTransactionId
should be defined asAlso, wouldn't
hex
instead ofalphanumeric
suffice as a constraint ontransactionId
?The text was updated successfully, but these errors were encountered: