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

Prerequisites should update based on user action

Abierto
#39 1 comentario 0 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
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
frontend

Línea de trabajo

Start by reviewing the OpenShift Quick start courses exploration document, especially pages 7 and 8, and inspect the current quick-start prerequisite behavior. Define whether prerequisites should update after user actions, whether unavailable quick starts should be locked or merely indicated, and how a cleanup script would reset the state; done means these behaviors and their edge cases are specified and implemented.

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

Descripción

enhancement

A script should be able to run that updates a quick starts prerequisites as the user completes them, giving users updated information about what they still have outstanding to complete before taking the current quick start. (Should be able to also run clean up script so the next person can run it again.)

This also brings up the question of how to handle quick starts that aren't available yet or when prerequisites haven't been completed. Are there any valid use cases for locking quick starts? Given that validation is still not possible, locking quick starts could just invite users to “fake” completion of a quick start to get to the next one. Additionally, we may not want to block advanced users from accessing a quick start later in a course if they don’t need the prior ones. If we find a valid use case for this, we could consider greying out and locking quick starts that users are not yet able to take. (Info on this pulled from OpenShift's Quick start courses exploration doc, page 7 and 8).

Jira Issue: PF-1893

Lenguaje dominante
TypeScript
Estrellas
15
Forks
47
Sin PR fusionados en 30 d

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 patternfly/patternfly-quickstarts

Todos los issues de patternfly/patternfly-quickstarts

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.