CodeYourFuture / CodeYourFuture/Module-Data-Flows
Book Library
- Linguagem predominante
- JavaScript
- Estrelas
- 0
- Forks
- 275
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
### Learning Objectives
- [ ] Fix known bugs in an application
- [ ] Use an application's specification to find any unknown bugs
### Link to the coursework
https://github.com/CodeYourFuture/Module-Data-Flows/tree/main/debugging/book-library
### Why are we doing this?
A big part of any development role is identifying and fixing bugs in code. Sometimes you will find these bugs yourself, other times users or colleagues will report them to you.
In this exercise we have provided some code which doesn't work properly. Start by running the code, then work through the list of bugs and attempt to fix them.
### Maximum time in hours
3
### How to get help
1. Share your blockers in your class channel. Use the opportunity to refine your skill in [Asking Questions](https://programming.codeyourfuture.io/guides/getting-help/asking-questions/) like a developer.
2. Use the debugger! Write tests! Use the tools you have been learning to help you solve problems methodically.
### Submission & Review
1. Fork to your Github account.
2. Make a branch for this project.
3. Make regular small commits in this branch with clear messages.
4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
```mermaid
gitGraph
commit id: "start"
branch feature/book-library
commit id: "skeleton page code"
commit id: "Fonts and colours"
commit id: "mobile layout"
commit id: "lighthouse audit revisions mobile"
commit id: "desktop layout"
commit id: "lighthouse audit revisions desktop"
checkout main
merge feature/book-library
```
There are several projects in this repo. [Make a new branch](https://simpledev.io/lesson/create-branch-gh-desktop-1) based on `main` for each project.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
Open the linked coursework in debugging/book-library and run the application first. Use the exercise specification to work through the known and unknown bugs, using the debugger and writing tests as needed. Done means the listed issues and any bugs found from the specification are fixed and the application works correctly.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- javascript
- Domínio
- testing-qa
- Tipo de issue
- Bug
- Dificuldade
- 3/5
- Tempo estimado
- 1-3 horas
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 35/100