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
{{ message }}
This repository has been archived by the owner on Jan 20, 2021. It is now read-only.
Instead of using the shape of the deployment.json provided by a protocol deployment, we should pass more specialized configuration object to the Environment. This would then allow us to provide custom token names, exchanges, etc. in a more controlled fashion. External systems, like our own frontend, can then do the job of translating a deployment file to this configuration object.
The text was updated successfully, but these errors were encountered:
Instead of using the shape of the deployment.json provided by a protocol deployment, we should pass more specialized configuration object to the Environment. This would then allow us to provide custom token names, exchanges, etc. in a more controlled fashion. External systems, like our own frontend, can then do the job of translating a deployment file to this configuration object.
The text was updated successfully, but these errors were encountered: