FungibleToken and NonFungibleToken Contract too strict (doesn't allow other states in same transaction)

[sandeepnRES]

Hi,

Can the contracts for FungibleToken and NonFungibleToken be relaxed, as right now it doesn't allow any state to be present in any of the transactions, except token.

But what if we want to use FungibleToken along with other states in some transactions, we could get help if you can relax the contracts, by checking only StateOfType<FungibleToken>?

Let's say we have IOU example, and we want to consume/update IOU state along with Tokens transfer, and the contracts commands like verifyMove doesn't allow the transactions to have IOUState and FungibleToken in this transaction.

Correct me if I'm wrong here. Also a quick reply would help, as we are working with a client for such use-case with a tight deadline.

[dineralex]

Agree with this issue. Each initiating flow must have a constructor with possibility to pass TransactionBuilder, such that initiator will be able to place additional states changes proposals into transaction. The token contract itself must have a hook for aditional validations for the issue,move and redeem, in the same way like EvolvableTokenContract have it.