Let's delete Workspaces.open(), since it's not adding any additional functionality and is pretty confusing. Same result can be achieved by excecuting Workspaces.init() and workspace.fork() functions.
The only test that was using open() function is rewritten and moved to the top-level __test__ directory. This is the only test that was using config object, we should add more in the future.
Currently, this test is failing, probably because of the https://github.com/near/workspaces-js/issues/128 issue. It was working fine with open() function.
open() and init() + fork() are handling config differently. I think this is the root cause of the problem. And one more reason to keep one API instead of two.
Let's delete
Workspaces.open(), since it's not adding any additional functionality and is pretty confusing. Same result can be achieved by excecutingWorkspaces.init()andworkspace.fork()functions. The only test that was usingopen()function is rewritten and moved to the top-level__test__directory. This is the only test that was usingconfigobject, we should add more in the future. Currently, this test is failing, probably because of the https://github.com/near/workspaces-js/issues/128 issue. It was working fine withopen()function.open()andinit()+fork()are handlingconfigdifferently. I think this is the root cause of the problem. And one more reason to keep one API instead of two.