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
Now, Force Bridge is using the docker to start the dev node, and a lot of work should be done before test starting. So I think we can change the way for Force Bridge to start dev by using kuai-cli.
The text was updated successfully, but these errors were encountered:
Now, Force Bridge is using the docker to start the dev node, and a lot of work should be done before test starting. So I think we can change the way for Force Bridge to start dev by using kuai-cli.
Sure, we may start using kuai-cli in our own projects too to iterate it in fast paces.
But before we do it, we may list the requirements of force bridge, and check if kuai-cli is competent for them. If not, how much work should we do on kuai-cli
Now, Force Bridge is using the docker to start the dev node, and a lot of work should be done before test starting. So I think we can change the way for Force Bridge to start dev by using kuai-cli.
Sure, we may start using kuai-cli in our own projects too to iterate it in fast paces.
But before we do it, we may list the requirements of force bridge, and check if kuai-cli is competent for them. If not, how much work should we do on kuai-cli
OK, I will list the things we could do after replacing verifier.
Now, Force Bridge is using the docker to start the dev node, and a lot of work should be done before test starting. So I think we can change the way for Force Bridge to start dev by using kuai-cli.
The text was updated successfully, but these errors were encountered: