Description:
The new syntax for comments in BigQuery allows the use of both # and -- for single-line comments. While the "Better Jinja" extension supports highlighting for the -- comment style, it does not currently highlight the # comment style in .sql files.
Expected Behavior:
Both -- and # should trigger comment highlighting when used in .sql files with Jinja context.
Current Behavior:
Only -- triggers comment highlighting.
Steps to Reproduce:
Open any .sql file with Jinja context.
Add a comment using the # symbol.
Observe that syntax highlighting is not applied to the # comment.
Potential Impact:
Developers accustomed to using # for comments may face readability issues, potentially impacting code quality and collaboration.
Inconsistent highlighting could lead to confusion regarding whether the syntax is valid or being interpreted correctly.
Suggested Solution:
Update the syntax highlighting rules to recognize # as a valid starter for a single-line comment in addition to -- when used in Jinja-SQL files.
Description: The new syntax for comments in BigQuery allows the use of both # and -- for single-line comments. While the "Better Jinja" extension supports highlighting for the -- comment style, it does not currently highlight the # comment style in .sql files.
Expected Behavior: Both -- and # should trigger comment highlighting when used in .sql files with Jinja context.
Current Behavior: Only -- triggers comment highlighting.
Steps to Reproduce:
Potential Impact:
Suggested Solution: Update the syntax highlighting rules to recognize # as a valid starter for a single-line comment in addition to -- when used in Jinja-SQL files.
Additional Context:
Reference to BigQuery’s updated syntax: BigQuery Standard SQL Lexical Structure