Can't create custom network

[austinabell]

Types weren't exported and the API doesn't support creating. #102 moves towards this, but some things are still not accessible.

For example NetworkClient trait required to use things requires returning a Client reference, but there is no way to construct a Client externally.

[ChaoticTempest]

Good point to mention. Some stuff might not be ready to allow users to construct their own network quite yet (such as the trait for top level account creation not having a good enough API), so was leaving this feature out for now. But definitely a good issue to tackle in the future to allow this

[bharath-123]

@ChaoticTempest i think what @austinabell suggests is useful because we might want to run our own sandbox and persist state between integration test runs. what do you think?

[ChaoticTempest]

This issue was more about creating a custom network where we can have custom behavior such as overriding calls into creating accounts via the helper contracts in testnet for instance. But for persisting state between sandbox, we have something like #64 which is currently blocked by how we can kill the sandbox after all tests have passed. You can use that if you need it now, but you'll potentially need to kill the sandbox yourself.

A simple way of getting the workflow you're suggesting (and having workspaces not manage the sandbox), is by specifying some configs in one of the initialization functions of workspaces. Probably an uncommon case to make use of, but could be worthwhile if you see value in wanting to start your own sandbox. Just note that this will end up making workspaces not have full control of sandbox, and then you will be the sole manager of it. This could mean resource leaks if you don't kill the sandbox after you're done with tests