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

[FR] Upgrade pop-up should only be shown to current owner, not users

Abierto
#815 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
typescript

Línea de trabajo

Search the TypeScript codebase for the “Upgrade” popup and the owner-role check, then reproduce the issue as a normal user and as a former owner. Trace how the current role is determined before upgrade-related UI is shown. Done means only users who currently have the owner role see the popup, while regular and former owners do not.

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

Descripción

Feature good first issue
Feature Description

As a normal user (no longer an owner), I encountered a pop-up prompting me to 'Upgrade'. This upgrade prompt should ONLY be shown to the current owner(s) of the sourcebot instance, not to users without the owner role.

Expected Behaviour:

  • The 'Upgrade' popup should be shown exclusively to users who currently have the 'owner' role.
  • Regular users (including former owners who no longer have the owner role) should NOT receive upgrade prompts.
  • The system should accurately check for the 'owner' role before displaying any upgrade-related UI elements.

User Story

  • When I sign in as a normal user, I should NOT receive upgrade prompts intended for organization owners. Only current owners of the organization should see the upgrade pop-up.
Lenguaje dominante
TypeScript
Estrellas
3.9k
Forks
374
Merge medio
21 h 18 min
PR fusionados (30 d)
39

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 sourcebot-dev/sourcebot

Todos los issues de sourcebot-dev/sourcebot

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.