Suggestions

Abierto
#251 1 comentario 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java

Línea de trabajo

The issue proposes several independent efforts: splitting HTMLReportGeneratorTest.java, reviewing dependencies, adding code review automation, cleaning files, adopting SonarCloud, and updating dependent repositories. Start by reading the repository contribution guidance and identifying which proposal maintainers want to pursue; the issue does not name tests or a single completion target, so clarify scope before estimating the work.

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

Descripción

So Currently some files are Too Long to manage Like HTMLReportGeneratorTest.java and etc I suggest we open a new branch and work on Files to part the files in new files.

Addition of Lombok dependency I know that the framwork works on the no abstraction but i feel like more maintainable code is nessecary. Any other dependency like those.

Addition of Code Reviewers:- reviewers like code rabbit are free of oss repos that review a pr for atleast 2 changes this will reduce the workload for the Owner.

CleanUp Cycle:- I suggest we start a cleanup cycle for each file at a time remove the import from each file that are not needed and variables white spaces, Try to Improve performance in some parts by understanding data structures if any. This gives more new first issues and new contributors a chance to pick those up.

Sonar Cloud:- As the whole framework depends on java we can put this on sonar cloud for oss that's free for free code smell detection.

Update Cycles:- the dependant repos like migrator my have new issues as the framework has added new features improving that will be a good idea.

Lenguaje dominante
Java
Estrellas
12
Forks
6
Merge medio
10 h
PR fusionados (30 d)
76

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 seleniumboot/selenium-boot

Todos los issues de seleniumboot/selenium-boot

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.