DTStack / DTStack/monaco-sql-languages

Colors...

Abierto
#178 1 comentario 0 reacciones 1 asignado Reclamado por @liuxy0551 Ver en GitHub
Lenguaje dominante
TypeScript
Estrellas
295
Forks
50
Merge medio
1 h 21 min
PR fusionados (30 d)
1

Descripción

Not really an issue, more a few improvements for colorization ;-)

Currently, I'm using the onigasm with vsdarkplus theme for pgplsql.
This is an example how my code looks like:

![Image](https://github.com/user-attachments/assets/837dc427-f069-445c-b1c8-73e4d6881d68)

When I paste this in your playground; I get the following:

![Image](https://github.com/user-attachments/assets/cc96862b-c7f2-456c-886a-bf0a5686b0ab)

A few things caught my mind:

1. The "replace" part of "create or replace" is recognized as function rather than statement.
2. The word "begin" at the start of the function body should be colored as control flow
3. The column- and table names have no special meaning, so the default colorizer keeps them uncoloured. In your version, I do not see a difference. I would imagine that I can feed a data model to the language server in order to perform auto complete and may be to colorize them in a special color when the table name is recognized (as Dbeaver now does, see below)
4. I changed one rule in the original colorizer: I colorize words that start with an underscore with an alternate color. That's just a personal taste because I always declare variables with underscores to prevent ambiguity. You can see the effect in the "select ... into..." part.

dbeaver example:

![Image](https://github.com/user-attachments/assets/be1937ca-b36a-4507-bdc5-19d35da82852)

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.