EditorConfig support as a "Generic" option for editor setup
Nadie ha tomado este issue todavía.
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
- Tranquilo
- Área
- cli, developer-experience, tooling
Línea de trabajo
Start by tracing the existing editor setup options for VS Code and Zed, then inspect the vp fmt and vp format entry points. Compare the current Oxfmt configuration with the requested .editorconfig behavior and define how conflicts should be reported or synchronized. Done means the scope and behavior of a Generic or EditorConfig option are implemented and verified.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
EditorConfig is a standard for configuring editors through one file (.editorconfig) instead of multiple (.vscode, .zed, .idea, etc)
A while ago, I suggested on the VoidZero Discord the idea of adding a generic option for editor setup, which would automatically create a .editorconfig file with as many formatting options that overlaps with Oxfmt.
I took a bit of a look at the specification, and admittedly it is quite small, so I'm not sure if this is something the team wants to take on and maintain. I'm willing to help if I can get some help in being pointed in the right direction to implement this.
Suggested solution
Like the image above tries to illustrate, there could be a new "Generic" or "EditorConfig" button that, when applied, creates a .editorconfig file that matches the default/current Oxfmt config (as much as possible).
When vp fmt/vp format is ran, it would check the EditorConfig file and the current Oxfmt file. If relevant configurations conflict from both .editorconfig and the Oxfmt config, there could be a printed warning that states that the configuration is not in sync and to run a command to sync the config? This part might be the fuzziest part of EditorConfig support to be honest.
Alternative
Selecting all the options in the menu, which is currently quite limited (as of writing, only contains VS Code and Zed)
Additional context
No response
Validations
- Read the Contributing Guidelines.
- Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- Check that there isn't already an issue requesting the same feature.
- Lenguaje dominante
- Rust
- Estrellas
- 5.8k
- Forks
- 263
- Merge medio
- 1 d 3 h
- PR fusionados (30 d)
- 147
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de voidzero-dev/vite-plus
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
voidzero-dev/vite-plus#2804 · 1 reacción ·
-
pending triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
voidzero-dev/vite-plus#2801 · 1 reacción ·
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
voidzero-dev/vite-plus#2097 · 10 comentarios · 2 reacciones ·
-
documentation
voidzero-dev/vite-plus#2800 · 1 asignado ·
-
pending triage
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
voidzero-dev/vite-plus#2796 · 1 comentario ·
Todos los issues de voidzero-dev/vite-plus
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
TheLarkInn/aipm#2413 ·
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
alexgorbatchev/simple-ptt#15 ·
-
tooling
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
todo:ticket
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
taikoxyz/taiko-mono#22168 · 1 comentario ·