Agentic coding support?

Abierto
#623 2 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
javascript

Línea de trabajo

El issue no menciona archivos, pruebas ni puntos de entrada. Empieza por mapear la arquitectura del editor del mono-repo de JavaScript y comprobar si ya existe una integración con LSP o agentic; define el panel de código, el límite de integración y los criterios de aceptación antes de la implementación.

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

Descripción

tl;dr: are you guys open to adding a cursor-like agentic coding pane (along with something like an LSP to support it)? If this already exists, I'm super sorry and would love a pointer!

My 9yo son is attending a coding camp again. I was speaking to him about his experience and learned that most of the kids spent their time googling and downloading games that other people had already developed. I asked him "but you must have ideas about how you'd like to change these games or tweak them, right?" and while he agreed, he said that it was "too much work". While part of me is sad that my kid is just not interested in learning the mechanics of coding, the other part of me recognizes that I haven't directly authored a single line of code in well over 6 months if not a year. And yet my productivity is roughly 10x and climbing, my code quality is up, test coverage up, etc. So... thoughts about adding agentic coding support?

The rather immediate counter argument, about "that's not how you learn to code" strikes me as enshrining the artisanship while underplaying the critical thinking aspect, which, at least for me, is brought to the fore by agentic coding work. I think this is one way to get kids experimenting, encourage and support curiosity, and I think that's a gateway to learning.

Lenguaje dominante
JavaScript
Estrellas
310
Forks
299
Merge medio
19 h 41 min
PR fusionados (30 d)
14

Preparar el entorno

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 scratchfoundation/scratch-editor

Todos los issues de scratchfoundation/scratch-editor

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.