Code intellisense/autocomplete

Abierto
#225 5 comentarios 0 reacciones 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript

Línea de trabajo

Start by locating the current code-editor integration and comparing it with the Wick Editor Legacy autocomplete shown in the issue. Review how VSCode-style suggestions could cover standard JavaScript, built-in functions, current-frame objects, and object members. Done means autocomplete is restored with a defined approach for objects whose visibility or definition order is uncertain.

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

Descripción

enhancement

Is your feature request related to a problem? Please describe.
Code editors usually have autocomplete, even the legacy version of Wick. It seems like it was removed when Wick went to 1.0.

Describe the solution you'd like
Bring back the autocomplete. It should be aware of standard JS stuff, our built-in functions, objects visible on the current frame, functions/variables defined in those objects, etc.

  • For objects visible on the current frame: remember that frames can be more than 1 long, so objects may or may not be visible for the whole time. I'm not really sure how we should deal with this. The safest way to do this is to show all objects, at the risk of some not being defined.
  • For functions/variables defined in objects: We can't really be sure of the order that objects are called in, so technically we will run the risk of things not being defined. I still think it's better to show everything possible.

Describe alternatives you've considered
You'd have to remember all the code you have, or use the outliner to remember what objects are on-screen.

Additional context
VSCode
Image

Wick Editor Legacy
Image

Lenguaje dominante
JavaScript
Estrellas
56
Forks
24
Merge medio
6 d 23 h
PR fusionados (30 d)
15

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 Candlestickers/Candlestick

Todos los issues de Candlestickers/Candlestick

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.