Feature Request: Support Pipe Syntax Formatting on DBx and BigQuery
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
The issue names no files, tests, or entry points. Start by reading the linked Databricks and BigQuery pipe-syntax references, then inspect the formatter's existing SQL dialect handling; done means pipe syntax from both platforms is formatted consistently.
Written by the indexing model from the issue text.
Description
Describe the Feature
Support formatting pipe syntax for Dabaricks and BigQuery.
In this syntax, SQL queries are expressed in a functional style using the pipe operator (|>), allowing operations like SELECT, WHERE, and GROUP BY to be chained together in a readable and modular way. Pipe syntax improves the clarity and structure of SQL by allowing queries to be written as a sequence of transformations, where each step builds on the previous one. This functional style enhances readability, especially for complex queries, by breaking them into logically organized components. It also promotes modular and maintainable code, making it easier to reason about and modify individual parts of a query. As a result, pipe syntax is becoming increasingly popular in modern data workflows and tools that emphasize composability and developer ergonomics.
Why do you want this feature?
Pipe syntax is increasingly being adopted for its readability and composability, especially in data platforms like BigQuery and Databricks. However, most SQL formatters, including this one, do not currently support it. Adding support for pipe syntax would help teams using modern SQL styles to maintain clean, readable, and consistently formatted code without needing to fall back to manual formatting or workarounds. This would be especially valuable in environments that prioritize functional or declarative query composition.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 456
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sql-formatter-org/sql-formatter
-
feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
sql-formatter-org/sql-formatter#951 · 4 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 54/100
sql-formatter-org/sql-formatter#942 · 1 comment ·
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 48/100
sql-formatter-org/sql-formatter#939 · 2 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
sql-formatter-org/sql-formatter#928 · 3 comments ·
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 56/100
sql-formatter-org/sql-formatter#914 · 7 comments ·
All issues in sql-formatter-org/sql-formatter
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:tools bug good first issue help wanted priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
TaewoooPark/Motifcode#14 ·
-
bug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
vercel/vercel-plugin#199 ·