TV Show Project Level 200: Swap Codebases
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- javascript
- Área
- frontend
Línea de trabajo
Comienza clonando el repositorio Project-TV-Show del colaborador y revisando su implementación de level 100 antes de realizar cambios de refactorización. Después implementa la búsqueda de episodios en tiempo real y el selector de episodios descritos en el issue, y verifica que funcionen los recuentos de coincidencias, el filtrado sin distinción entre mayúsculas y minúsculas, la limpieza de la búsqueda y la selección de un episodio antes de abrir un pull request para que el colaborador lo revise.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Level 200
For level 200, you are not allowed to work on the same codebase as you worked on for level 100.
Swap repos with a random person in your class. You may find it helpful to do this first step together:
- Go to your copy of
Project-TV-Showand click on the setting - Go to the "collaborators" section
- Next "manage access", click "add people"
- Type the username your partner
- Click the green add button
- Visit the URL for your partner's project and accept the invitation to collaborate / check your email for the invite link
- Clone your partner's repository to your laptop, you will need to give it a different name, such as
Project-TV-Show-THEIR_NAME
Now, work individually to complete level 200:
Look at their level 100 implementation.
Compare their implementation to yours. Think:
- How is it different?
- What do you prefer about your implementation?
- What do you prefer about their implementation?
- What did you learn that you didn't know before?
They should do the same with your repository.
Have a discussion about your answers to these questions. In class, together you should give talk for 5 minutes about your conclusions. (Do this in small groups - we don't want to take all day).
Refactoring
Before implementing new features, take some time to change the codebase you're going to build level 200 in. Change anything you think will make it easier to add more features.
Some example ideas that you may want to think about:
- Could any variables or functions have more clear names, to help you understand what they do?
- Would extracting functions help make some code easier to understand?
Work in a new branch on your partner's repo, making any changes you think are useful.
Then make a pull request to your partner's main branch (take care not to PR to the CYF main branch yet).
Have them review, and when happy, merge your PR.


Adding new functionality
Level 200 is all about being able to filter episodes.
Search
Add a live search input which meets the following requirements:
When a user types a search term into the search box:
- Only episodes whose summary OR name contains the search term should be displayed
- The search should be case-insensitive
- The display should update immediately after each keystroke changes the input
- Display how many episodes match the current search
- If the search box is cleared, all episodes should be shown
Send a pull request to your partner's repo with this functionality. Have them review, and when happy, merge your PR.
Screenshot of minimal version
Note: Provided your project meets the above requirements, it can look however you want.
Here is one example layout.

Episode selector
Add a select drop-down which lets the user jump quickly to a particular episode, with the following requirements:
- The select input should list all episodes in the format: "S01E01 - Winter is Coming"
- When the user makes a selection, they should be taken directly to that episode in the list
- Bonus: if you prefer, when the select is used, ONLY show the selected episode. If you do this, be sure to provide a way for the user to see all episodes again.
Send a pull request to your partner's repo with this functionality. Have them review, and when happy, merge your PR.
Screenshot of minimal version
Note: Provided your project meets the above requirements, it can look however you want.
Here is one example layout.

- Lenguaje dominante
- JavaScript
- Estrellas
- 0
- Forks
- 276
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CodeYourFuture/Module-Data-Flows
-
Complete the ITP end survey Abierto🏕 Priority Mandatory 📅 Sprint 3 Core Module-Data-Flows Submit:None 🦔 Size Tiny
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
Prepare a demo for Q&A workshop Abierto🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Data-Flows Submit:None
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 3 Core Module-Data-Flows Submit:None
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Flows Submit:None
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 1 Core Module-Data-Flows Submit:None
Dificultad 1/5 1-3 horas Aptitud para principiantes 35/100
Todos los issues de CodeYourFuture/Module-Data-Flows
Issues similares
-
bug confirmed issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
open-webui/open-webui#30750 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Mend: dependency security vulnerability untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100