Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Service Management: Single Page Overview

Abierto
  • ¿Algo no está bien?
#36,099 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
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
typescript
Área
design, frontend

Línea de trabajo

Start by locating the settings view and the existing services settings pages; the issue does not name files, tests, or entry points. Review how connector categories and settings navigation work, then assess what needs to change to show all services in one table at the proposed route and link to it from settings. Done means users can reach the overview from the settings tile and manage connectors from the single page.

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.

Managing connectors is a primary task because they are the main driver for the catalog content.
However, there are some UX problems here.

  1. Locating the settings. Connector settings are reachable from host.tld/settings. The user has to click on the card titled "Services" which is vague and should be titled "Connectors", "Sources", or "Ingestion" instead, which is more standard and would actually match the card description, which reads "Set up connectors and ingest metadata from diverse sources"
  2. Getting an overview of connectors. Connector settings are managed from host.tld/settings/services. However, to get an overview of all connectors, the user has to click through 11 cards (APIs, Databases, Messaging, Dashboards, Pipelines, etc.) only to find (on an average instance) most of these categories to be empty. Should the user also wish to see deleted connectors, all 11 categories have to be navigated and the "Deleted" switch has to be clicked 11 times.
  3. Editing a specific connector. Specific connector settings for a certain category are reachable from host.domain/settings/services/. While I know exactly the category of the connector (usually database, pipeline or dashboard) finding the correct tile among the 11 (visually not very distinctive) categories on host.tld/settings/services is cumbersome.

All in all, the category tiles are not the best way to organise connectors because

  • this is overkill. The number of overall connectors is expected to be small, I'd say usually ≤ 20. Listing them all would be much more user friendly. Even if there was a need to organize contents hierarchically, a tree view would be better, because you can have the contents of multiple categories expanded at once.
  • this overkill leads to most categories being empty or having only very few entries. The experience of navigating into a category to find it empty and having to navigate out of it again is not good.
  • the tiles give the user an overview of what categories there are, while the user actually wants to know what connectors there are
  • the tiles appear to be in random order (not alphabetically, not by importance, not by similarity) and even if they were ordered, a grid structure wouldn't be a great fit to convey their order
  • the icons are inconsistent with the icons used in the Browse Estate tree view (e.g., Dashboards and Pipelines)
Describe the solution you'd like

Display all services in a single table under host.tld/settings/connectors

Image

That page should be reachable from a "Connectors" tile in the settings view.

Image
Describe alternatives you've considered
  • Do not show category tiles for empty categories (e.g., there might be nothing under "ML Models" or "Search"). Not displaying tiles for empty categories would reduce the chance of users navigating into dead ends. But this would not remove the superfluous navigation step and it would not relief the user from having to deal with a connector taxonomy that provides little benefit.
  • Show how many connectors are in each category on the category tile. So the user has a coarse overview what exists in the instance and where. Alleviates but does not eliminate the above mentioned problems.
  • Adding connector settings to the top level side bar menu. However, I prefer the current focus on catalog contents rather than catalog settings.
Additional context

No response

Pre-submission checklist
  • I searched for duplicate feature requests.
Lenguaje dominante
TypeScript
Estrellas
15.4k
Forks
2.4k
Merge medio
1 d 1 h
PR fusionados (30 d)
699

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 open-metadata/OpenMetadata

Todos los issues de open-metadata/OpenMetadata

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.