You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The same issue as reported in #1680 (var-naming warns on variables with dynamically set names) and fixed in #1988 (See file diff) was then later undone in #3422 , but that commit does not appear to have been about var-naming[no-jinja]. In fact the comment from the original fix is still present,
# We want to allow use of jinja2 templating for variable namesif"{{"inident:
so I can only assume that the removal of the return False was not intentional.
The same issue as reported in #1680 (
var-naming
warns on variables with dynamically set names) and fixed in #1988 (See file diff) was then later undone in #3422 , but that commit does not appear to have been aboutvar-naming[no-jinja]
. In fact the comment from the original fix is still present,so I can only assume that the removal of the
return False
was not intentional.Can the behaviour post #1988 be restored?
The text was updated successfully, but these errors were encountered: