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
Famous last words. This requires changes in quite a few places. Right now we support unaries in front of numbers by lexing the operator as a part of the number, but that approach won't work generally, since we have to support any expression after the operator. So this will require a new token type and maybe a new lexing ruleset, and then a close look at the line merging logic.
Describe the bug
When unary operators are used in column definition X, X is formatted to be in the same line as the previous column definition.
A space is also added in between the unary operator and the operand (not sure if this is expected).
To Reproduce
Expected behavior
I expect the code above to remain unchanged after formatting with a maximum line length of 88
Actual behavior
This is sqlfmt's output:
Additional context
This is reproducible from
https://sqlfmt.com/
The text was updated successfully, but these errors were encountered: