lint - S011 no longer warns against 0{{a}} #5841
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously something like
a = $((10#$foo)) {{ bar }}
would trigger S011 in Cylc Lint, assuming that this was jinja after a comment. I've made it ignore this synatx. By ignoring this syntax there is of course a potential that#$ a real comment {{ jinja }}
will be ignored, but I think it quite unlikely an edge case which would require making the regex more complex to work through.This is not a perfect fix for #5682 but an improvement. Perhaps a sufficient enough fix that it can be closed though.
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).CHANGES.md
entry included if this is a change that can affect users?.?.x
branch.