Add Kotlin as an optional language group in Whiteboard Desktop

Abierto
#1,092 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@sidkmenon ya está trabajando en esto.

Desde el 14/10/2026.

  • #1248 de @sidkmenon — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, kotlin, typescript

Línea de trabajo

Read the existing Go group in reviewOptionalExtensionCatalog.ts, reviewCuratedExtensions.contribution.ts and scripts/curated-extensions.manifest.mjs, then review the LSP telemetry files and scripts/e2e/lsp-languages.mjs. First resolve the open question about which Kotlin extension to use; the issue says it is waiting for the approach to be confirmed. Done means adding the catalog, telemetry and Kotlin and Gradle Kotlin DSL LSP journey, then running the listed validation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

Kotlin files get no syntax highlighting and no language server in Whiteboard Desktop. This covers .kt sources and Gradle Kotlin DSL build files (build.gradle.kts, settings.gradle.kts). Groovy Gradle files (build.gradle) already highlight through the bundled groovy extension.

Android and Kotlin Multiplatform projects use Kotlin almost everywhere, including their build files. Reviewing them in Whiteboard today means reading plain text, with no go-to-definition, hover or references.

The marketplace is disabled, so users cannot add a Kotlin extension themselves.

Proposed approach

Add a kotlin group to the optional extension catalog, following the existing Go group:

  • reviewOptionalExtensionCatalog.ts: a pinned Open VSX VSIX entry for the kotlin group.
  • reviewCuratedExtensions.contribution.ts: a "Kotlin" option, with a detail line saying it needs a Java runtime on the machine.
  • scripts/curated-extensions.manifest.mjs: the matching manifest entry.
  • reviewLspTelemetry.contribution.ts and docs/telemetry.md: add kotlin to the review_ls_activated group values.
  • scripts/e2e/lsp-languages.mjs and a lsp-kotlin journey: open a small Kotlin and Gradle Kotlin DSL fixture and check hover and go-to-definition.

Open question: which extension

Option Highlighting Language server Notes
fwcd.kotlin 0.2.36 (Open VSX, MIT) Yes kotlin-language-server, needs a JVM Universal VSIX. Last release December 2024.
JetBrains kotlin-lsp Yes Official JetBrains server Not on Open VSX, so it would need a different download source. Pre-release status.
Grammar only, such as mathiasfrohlich.Kotlin 1.7.1 (Open VSX, Apache-2.0) Yes No No runtime dependency. Unmaintained since 2020.

Which of these would you accept? Grammar-only could also ship first, with a server added once one is chosen.

Validation plan

  • Run pnpm run ci.
  • Run the new Kotlin LSP journey.
  • Check a real Android project by hand: highlighting in .kt and .kts files, hover, go-to-definition and references in the Files tab and the Diff view.

I'm happy to send the pull request once the approach is confirmed.

Lenguaje dominante
TypeScript
Estrellas
2.9k
Forks
145
Merge medio
15 h 50 min
PR fusionados (30 d)
489

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devdotfast/whiteboard

Todos los issues de devdotfast/whiteboard

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.