Show which plugins an app loads, and scope a plugin's pages to that app

Abierto
#2,037 0 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start with src/features/instance/extensions/parseStudioConfiguration.ts to understand page keys, then trace navigation links in useInstanceNavLinks.tsx and the Applications and plugin management pages. The proposal also depends on Harper's get_studio_configuration reporting which app loads each plugin. Done means apps link to their plugins, plugin pages link back to loading apps, and settings are scoped to the selected app.

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

Descripción

Problem

Once plugins are loaded by apps, nothing connects the two in Studio, and a page can't tell which app it is configuring (#2031):

  • Opening an app in the Applications tab doesn't show the plugins it loads.
  • A plugin's page doesn't show which apps load it.
  • The same plugin can be loaded by two apps with different settings, but a page key of <component>.<id> names only the plugin.
Proposal
  • In Applications, list the plugins an app loads, each linking to its management page, and on a plugin's page list the apps that load it, linking back.
  • Make the app part of a page's identity, as <app>/<plugin>.<id> or as a context the page is opened with, so a settings page edits one app's configuration.

Harper's get_studio_configuration (HarperFast/harper#3656) would need to report which app loads each plugin.

Context

Raised in review of #2031 (comment). Code: src/features/instance/extensions/parseStudioConfiguration.ts (page keys) and useInstanceNavLinks.tsx.

🤖 Generated by Claude Code (Claude Opus 5.5); posted via @dawsontoth.

Lenguaje dominante
TypeScript
Estrellas
5
Forks
4
Merge medio
2 d 13 h
PR fusionados (30 d)
60

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 HarperFast/studio

Todos los issues de HarperFast/studio

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.