Fix Twig/Jinja: incorrect recognition of some special tokens like keywords #1949
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.
Bug
Twig and Jinja may return incorrect token types for some special tokens like keywords. It depends on loading order.
cf. #1939 (comment)
Cause
Twig
andJinja
lexers share class variables. Both classes definekeywords
method like this:If
Twig.keywords
is called beforeJinja.keywords
,@@keywords
is set to Twig's and both methods return the same value. If not,@@keywords
is initialized to Jinja's.Solution
I changed class variables to instance variables. Other lexer classes define their keywords as instance variables.