iiiiiiii

This is a very good point. But I don't think we won't support `contract.transfer(signer.address)).rejectWith(Error.InsufficientAllowance)` of this form. Instead, it will support matching errors using strings. Like this `contract.transfer(signer.address)).rejectWith("InsufficientAllowance")` . Because...

I had a look at the swanky suite. redspot is mainly used for integration testing, similar to hardhat and waffle on eth, but I don't see these things on swanky.

#117

As far as I know, hardhat doesn't provide a deploy command either, https://hardhat.org/tutorial/deploying-to-a-live-network.html#_7-deploying-to-a-live-network. Did I miss something?

You mean the deploy function? Can't this function work? https://github.com/patractlabs/redspot/blob/master/examples/erc20/scripts/deploy.ts#L24

Well, I think it does look OK. We'll add this in the next version.

@KaiserKarel Are you using @redspot/known-types. If so then there is a real possibility of a conflict, if not then it should be fine.

First you can check if the types have been correctly injected into the api.registry. For example: 1. redspot.config.ts should look like this: ``` ... networks: { development: { endpoint: "wss://kusama-rpc.polkadot.io",...

Of course you can't do that. there is no problem with this error. The first parameter of createType is the type name and the second parameter is the value. https://polkadot.js.org/docs/api/start/types.create...

`decodeU8a: failed at 0x5901000000000000… on bar: Text:: Text: required length less than remainder, expected at least 88, found 50` I think the type should already be injected. This error does...