Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handlebars replacement for contextual information #1100

Open
hardyjosh opened this issue Dec 19, 2024 · 0 comments
Open

Handlebars replacement for contextual information #1100

hardyjosh opened this issue Dec 19, 2024 · 0 comments
Assignees

Comments

@hardyjosh
Copy link
Contributor

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:

  1. Using token addresses from the current order being deployed in the scenario bindings
  2. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants