Self reports: Second delivery

[UO283615]

Please comment on this issue with your self reports. Remember to vote on each other's reports and to follow the template that we used in the previous one.

[gony02]

For this delivery I worked on:

Pull requests 🪢

Related with the Documentation:

• chore: fixing some tables, plantuml diagrams and writing a title for … #54
• chore: improving the main readme and adding the wireframes. #99

Related with the webapp:

• Feat/webapp/new login #64
• Feat/webapp/new signup #65
• Feat/webapp/new dashboard #79
• feat: adding the login tests. #90
• fix: fixing the loginTests to work correctly. #94
• Feat/webapp/new game #102

Issues ✍️

I have collaborated in the following issues:

• Enable HTTP/2 #51
• Version naming #53
• Developing the login page #59
• Developing the signup page #60
• Fix unit tests actions for frontend #67
• Bug report: possible CORS problem when networking the webapp to the API #69
• Developing the user's dashboard page #74
• Developing the Game view #80
• Add the wireframes to the documentation #95

Wiki 📖

Moreover, I have written several pages on the Wiki and I have actively engaged in various meetings. I have not participated in the meetings focused in the backend.

• Home
• 20/02/2024
• 23/02/2024
• 27/02/2024
• 03/03/2024
• 05/03/2024
• 08/03/2024 frontend
• 10/03/2024

Other 👨‍💻

For this second delivery, I have designed all the wireframes of the application that I have included in the documentation (see Section 2: Integration constraints). Then I made the Login and Logout views in React with Chakra UI with @sergiorodriguezgarcia doing pair programming. Then I made the Dashboard, Rules and Game views. Additionally I have communicated the Game and Rules views with the backend. Finally, I have done unit tests of different views of the webapp trying to have at least 80% coverage in SonarCloud.

[sergiorodriguezgarcia]

For this delivery I worked on:

Pull requests 🪢

Related with the documentation:

• feat: Adding the icon image to the documentation #113
• Feat/delete help docu #114

Related with the webapp:

• Feat/webapp/new login #64
• Feat/webapp/new signup #65
• feat: Adding the home page and tests for it #84
• fix: fixing the loginTests to work correctly. #94
• Feat/webapp/new game #102
• Feat/add tests #108

Issues ✍️

I have collaborated in the following issues:

• Enable HTTP/2 #51
• Version naming #53
• Developing the login page #59
• Developing the signup page #60
• Fix unit tests actions for frontend #67
• Bug report: possible CORS problem when networking the webapp to the API #69
• Developing the user's dashboard page #74
• Developing the Game view #80
• Add the wireframes to the documentation #95

Other 👨‍💻

I have made the Login and Logout views in React with Chakra UI with @gony02 doing pair programming. Then, I made some fixes in the Dashboard and game views and additionally, I have communicated the Signup view with the backend and implemented the Logout logic. Finally, I have done unit tests of different views of the webapp trying to have at least 80% coverage in SonarCloud.

[sergioqfeg1]

For this delivery I worked on:

Pull requests 🪢

Related with the API:

• Hotfix/question language #104
• Added dummy data generation for testing purposes #89
• Fixed mistakes found within AnswerQuestion and started testing of QuestionController/QuestionService #86
• Feat/questions #71

Issues ✍️

I have collaborated in the following issues:

• Create dummy data for questions and answers for testing frontend #73
• Bug report: possible CORS problem when networking the webapp to the API #69
• Bug report: POST to API endpoint /auth/login returns 403 error in Postman and fails in the browser #66
• Questions endpoints #57
• Version naming #53
• Enable HTTP/2 #51
• Regarding localization #6

Other 👨‍💻

For this seciond delivery my job as part of the backend team, was to develop the controllers, services and repositories for the Springboot API along side @Toto-hitori. We had several pair programming sessions developing the end points and the logic of saving/getting questions and answers. We also developed several tests for the endpoints and the services. I also edited the part 5 and 12 of the documentation.

[GOLASOOO]

For this delivery I worked on:

Pull requests 🪢

• chore: fixing some tables, plantuml diagrams and writing a title for … #54
• Code cleanup and http2 in API #55
• Feat/questions #71
• Removed Roles table and included it as a String column in the User table #85
• Feat: Questions and answers are now written in the DB! #97
• Feat/webapp/new game #102
• fix: question generator bugs #103
• fixed docker compose thing #110
• chore: fixed name on docker images #111
• chore: .env file in webapp #112

Issues ✍️

I have collaborated in the following issues:

• Version naming #53
• Connect to the database for storing the questions #81

Other 👨‍💻

During this sprint, I teamed with @UO283615 to implement the QuestionGenerator module, which has two parts. The first one, querying questions from WikiData QS and the second one, processing and storing the responses into the DB.
The first week we did research and discussions about how to implement it so no code was created. On the second week, Villanueva had more spare time than me so he implemented the module and in the third week I did code clean ups and documented the code so other members of the team can create their own questions easily.
I also supported @Toto-hitori with the deployment and bug solving from frontend and backend.

[jjgancfer]

For this delivery I have worked on:

Pull requests 🪢

Reviewed pull requests

• chore: fixing some tables, plantuml diagrams and writing a title for … #54
• Added tests for the Authentication endpoints #62
• Feat/webapp/new login #64
• Feat/webapp/new signup #65
• fix: invalid credentials now returns descriptive error instead of generic one #68
• fix: cors configuration origins #70
• chore: created actions for deployment and unit testing of Spring Boot API #75
• fix: broken question controller test #76
• Feat/webapp/new dashboard #79
• feat: Adding the home page and tests for it #84
• Removed Roles table and included it as a String column in the User table #85
• feat: logout endpoint #87
• feat: adding the login tests. #90

Created pull requests

• Code cleanup and http2 in API #55
• chore: webapp routing rewrite #56
• Feat/webapp/new login #64
• Feat/webapp/new signup #65
• feat: Adding the home page and tests for it #84

Issues ✍️

I have collaborated in the following issues:

• Regarding localization #6
• Enable HTTP/2 #51
• Add architectural decisions to wiki #63
• Bug report: POST to API endpoint /auth/login returns 403 error in Postman and fails in the browser #66
• Fix unit tests actions for frontend #67
• Bug report: possible CORS problem when networking the webapp to the API #69
• Add logout endpoint to Authentication Service #78

Other 👨‍💻

In this sprint, I started developing a new login page before passing that task to @gony02. With him and @sergiorodriguezgarcia, we agreed to discard to the layout initially written in the previous sprint in favour of another. We also teamed up to introduce initial communication between backend and frontend.

Finally, these last days I have included several architectural decisions in the wiki.

[UO283615]

For this delivery I worked on:

Pull requests 🪢

Related with the Documentation:

• Some updates in the documentation #98

Related with the question generator:

• Feat/questions #71
• Feat: Questions and answers are now written in the DB! #97

Issues ✍️

I have collaborated in the following issues:

• Add architectural decisions to wiki #63
• Connect to the database for storing the questions #81
• Version naming #53
• SPARQL #11
• Generating the questions #12

Wiki 📖

Moreover, I have written a page on the Wiki and I have actively engaged in various meetings. I have not participated in the meetings focused in the frontend.

• Home

Other 👨‍💻

To sum up I focused on the question generator. Specifically, I learnt how to communicate with Wikidata from Java and how to connect with the DB. Also I helped on the design of the data model.

[Toto-hitori]

For this delivery I worked on:

Pull requests 🪢

Related with the Documentation:

• Chore/gonzalo a/docu #36

PRs:

• Added tests for the Authentication endpoints #62
• fix: invalid credentials now returns descriptive error instead of generic one #68
• fix: cors configuration origins #70
• Feat/questions #71
• chore: created actions for deployment and unit testing of Spring Boot API #75
• fix: broken question controller test #76
• Added Java Spring Boot project to SonarCloud  #82
• Removed Roles table and included it as a String column in the User table #85
• Fixed mistakes found within AnswerQuestion and started testing of QuestionController/QuestionService #86
• feat: logout endpoint #87
• Added dummy data generation for testing purposes #89
• Feat/webapp/new game #102
• Hotfix/question language #104

Issues ✍️

I have collaborated in the following issues:

• Add logout endpoint to Authentication Service #78
• Add Spring Boot API to SonarCloud's coverage #77
• Create database definition script for Spring Boot API #72
• Bug report: possible CORS problem when networking the webapp to the API #69
• Bug report: POST to API endpoint /auth/login returns 403 error in Postman and fails in the browser #66
• Add SpringBoot tests to Github actions  #61
• Questions endpoints #57
• Version naming #53
• Deploy Spring + React application with Github actions #58
• Deploy Spring + React application with Github actions #58
• Have i mentioned Deploy Spring + React application with Github actions #58?

Wiki 📖

Moreover, I have written several pages on the Wiki and I have actively engaged in various meetings. I have not participated in the meetings focused in the frontend.

• Home
• 20/02/2024
• 27/02/2024
• 03/03/2024
• 05/03/2024
• 10/03/2024

Other 👨‍💻

For this second delivery, I have lost my sanity trying to deploy the api and the webapp, having spent multiple hours deploying and looking into github actions. yay :)

[GOLASOOO]

Closed as second delivery review has already been done.