Allow unzipped source archives

Abierto
#1,324 1 comentario 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
typescript, vscode
Área
tooling

Línea de trabajo

Comienza leyendo el archive-filesystem-provider existente y el comportamiento de su file-explorer. Evalúa cómo un directorio de un sistema de archivos normal podría usar la misma API que la variante basada en zip y seguir siendo de solo lectura. Se considerará completado cuando las carpetas de código fuente de bases de datos descomprimidas puedan mostrarse y utilizarse sin permitir ediciones, junto con los archivos zip existentes.

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

Descripción

enhancement VSCode

Background

This feature request is about allowing unzipped database source archives in addition to zipped source archives. Historically, we allowed unzipped archives, but it was challenging to maintain multiple ways of interacting with sources as we grew the number of features that the extension supported. Also, users would sometimes inadvertently edit the unzipped sources and sometimes even expect that the database would be transparently updated to handle the new sources.

Previously, we had allowed unzipped database sources to be imported as regular folders into the project. This would signal to users that they could edit the sources, which should not be possible.

Proposal

Currently, we have created the archive-filesystem-provider, which displays the contents of zip files in the file explorer in read-only mode.

I think we should be able to extend archive-filesystem-provider so that there are two variants: one variant is backed by a zip file and the other is backed by a regular file system directory. Of course, this would mean that the name archive-filesystem-provider is no longer really appropriate, but that is a minor issue.

The benefit is that we can read in the source folder of a database and ensure that even though the file explorer points to regular files, everything is read-only. And we will also be able to interact with both kinds of filesystems through the same API even though they are differently implemented.

Lenguaje dominante
TypeScript
Estrellas
539
Forks
240
Merge medio
2 d 6 h
PR fusionados (30 d)
29

Guía de contribución

Abrir la guía de contribución

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 github/vscode-codeql

Todos los issues de github/vscode-codeql

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.