google / google/google-sql-syntax-ts
General Issues with formatting result
- Langage dominant
- TypeScript
- Étoiles
- 10
- Forks
- 4
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hi @Ekrekr, I've been following your work in [dataform](https://github.com/dataform-co/dataform), and I was pleasantly surprised to see that this repository existed, as we wanted to understand how formatting works in the BQ UI.
I want to build a VSCode extension and tooling based on this, to standardize SQL formatting and have the same format between `dataform`, `BQ UI` and `Airflow` SQL.
The best formatter currently which is also compatible with jinja is SQLfluff, and produces very good results once configured.
One of our main problems with the current way formatting works is that the result for complex queries is completely unreadable for a human. Ideally the formatter would format based on some standards such as:
- https://www.sqlstyle.guide/
- https://handbook.gitlab.com/handbook/business-technology/data-team/platform/sql-style-guide/
I would be in general interested in forking this and start hacking on it a bit whenever I have time, and/or provide some examples of how the output can be made more readable.
Lastly, I have a general question: would a change/suggestion in here be applied to the Monaco Editor under the BQ UI?
Thank you for taking your time to read this, and sorry for the long wall of text
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par examiner le comportement actuel du formatage du dépôt et comparez la sortie des requêtes complexes avec le SQL Style Guide et le GitLab SQL style guide liés dans l’issue. Utilisez le formateur SQLFluff et les exemples fournis par l’auteur du signalement comme points de comparaison, puis déterminez si des modifications apportées ici affecteraient le Monaco Editor dans la BigQuery UI.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- sql, typescript
- Domaine
- developer-experience, tooling
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100