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
{{ message }}
Repository navigation
Feature Request: Line break before or after "+" #796
Describe the Feature
When building a long string in a script for insert or update, I like to break it into logical chunks for readability and easy maintenance. Also, VSCode does not like really long single-line strings. Something like this:
Unfortunately this is very unlikely to get implemented in SQL Formatter, because I'm not really doing any real feature development in this library. Rather I'm concentrating on prettier-plugin-sql-cst, which is much more likely to support such a thing in the future, as its architecture is much better suited for that.
Hard to say. Currently the main priority is to get PostgreSQL supported. Then MySQL/MariaDB. Given that SQL Server is proprietary, it's also harder implement support for it. Like with PostgreSQL I have often dug into PostgreSQL source code to figure out which syntax exactly is supported. With SQL Server I've always found the documentation to be one of the most confusing among SQL dialects. So I'm personally not really keen on implementing a parser for it :(
Activity
nene commentedon Nov 4, 2024
It's a very reasonable feature request.
Unfortunately this is very unlikely to get implemented in SQL Formatter, because I'm not really doing any real feature development in this library. Rather I'm concentrating on prettier-plugin-sql-cst, which is much more likely to support such a thing in the future, as its architecture is much better suited for that.
gwduvalljr-AT commentedon Nov 4, 2024
gotcha
I checked out the prettier plugin. I use prettier every day. We are a SQL Server shop. Any idea when tsql will be supported?
nene commentedon Nov 4, 2024
Hard to say. Currently the main priority is to get PostgreSQL supported. Then MySQL/MariaDB. Given that SQL Server is proprietary, it's also harder implement support for it. Like with PostgreSQL I have often dug into PostgreSQL source code to figure out which syntax exactly is supported. With SQL Server I've always found the documentation to be one of the most confusing among SQL dialects. So I'm personally not really keen on implementing a parser for it :(