We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A niche interaction between:
this
any()
duplicate=true
This example:
# meta/rose-meta.conf [namelist:a] duplicate=true [namelist:a=var] fail-if=any(this == "foo") length=:
# rose-app.conf [namelist:a] var=foo
Will fail validation:
$ rose macro -V [V] rose.macros.DefaultValidators: issues: 2 namelist:a=None=None incorrect "duplicate=true" metadata namelist:a=var=foo failed because: any(this == "foo")
Whereas this example:
# rose-app.conf [namelist:a(1)] var=foo
Will not:
$ rose macro -V
From inspection it would appear the REC_CONFIG_ID regex is including the opening bracket in the varible name.
REC_CONFIG_ID
I.E. it is matching:
(namelist:a(1)=var(1)
Rather than:
namelist:a(1)=var(1)
Due to some, curious, logic, this error gets swallowed rather than resulting in traceback.
Replace this with the full name of the config.
# meta/rose-meta.conf [namelist:a] duplicate=true [namelist:a=var] fail-if=any(namelist:a=var == "foo") length=:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A niche interaction between:
this
any()
duplicate=true
metadata configurationReproducible Example
This example:
Will fail validation:
Whereas this example:
Will not:
$ rose macro -V
Cause
From inspection it would appear the
REC_CONFIG_ID
regex is including the opening bracket in the varible name.I.E. it is matching:
Rather than:
Due to some, curious, logic, this error gets swallowed rather than resulting in traceback.
Workaround
Replace
this
with the full name of the config.The text was updated successfully, but these errors were encountered: