Hey all, I have an issue with the yaml linter It r...
# yaml
g
Hey all, I have an issue with the yaml linter It red underlines any variable not listed in the
variables:
section. Including values from the
config:
section, and also from the stack files, or inherited from imported ESC environments Ideally it will look at the stack variables and the imported ESC environments, but I understand this may be hard I'd accept a workaround like naming variables with a certain prefix to tell the linter "this variable comes from somewhere outside of this file"
image.png
e
Hey just saw this. Can you declare these variables in the config block, and just not give them a value so they continue picking up the values from esc/stackfile but the linter will know about them?
g
I could but that would be duplication of work, what if I have 30 variables in my stack config (and many in my
config:
section. It would become hard to maintain. The example I gave above is one of the most simple I have