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
There are two initial use-cases for this kind of replacement:
Using token addresses from the current order being deployed in the scenario bindings
Using token name/symbol current order being deployed in the names/descriptions of GUI fields
In both cases, the order is in context because we know the deployment, and the order is part of the deployment.
If we were accessing the scenario bindings outside of a deployment context (e.g. for making charts) then there is no order in context. This should just be an error.
I'd suggest to create a new YamlContext struct and pass it through so that when a Deployment gets its Scenario, the Deployment passes its context through to the scenario getter.
The text was updated successfully, but these errors were encountered:
We are using inspiration from Github for this https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs
There are two initial use-cases for this kind of replacement:
In both cases, the order is in context because we know the deployment, and the order is part of the deployment.
If we were accessing the scenario bindings outside of a deployment context (e.g. for making charts) then there is no order in context. This should just be an error.
I'd suggest to create a new
YamlContext
struct and pass it through so that when aDeployment
gets itsScenario
, theDeployment
passes its context through to the scenario getter.The text was updated successfully, but these errors were encountered: