-
Notifications
You must be signed in to change notification settings - Fork 5
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
Feature/ioc boot #18
Feature/ioc boot #18
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great.
@@ -0,0 +1,31 @@ | |||
# yaml-language-server: $schema=file://schemas/ibek.schema.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like epics.ibek.yaml.
There are probably other things that would go in here I'm guessing.
epicsEnvSet "EPICS_TS_MIN_WEST", '0' | ||
cd "$(TOP)" | ||
{% if env_var_elements %} | ||
{{ env_var_elements -}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've never seen this syntax before, what does it do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's syntax for control structures, in this case I just check to see if env_var_elements is defined - https://jinja.palletsprojects.com/en/3.0.x/templates/#list-of-control-structures
This was just to keep the boot script tidy, as I found it difficult to control new lines with optional elements.
This PR contains a set of small changes based on generating the ioc boot script: