Meeting 2 of 352‐Backend - bounswe/bounswe2025group5 GitHub Wiki
Details
📅 Date: 12/04/2025
📍 Location: Zoom
🕐 Duration: 21.30 - 22.30
📝 Note Taker: Cengiz Bilal Sarı
👥 Attendees
Agenda
- Decision of the endpoints that needed in the flow.
- Separation of the endpoints to the individuals.
Information about the Endpoints:
-
Login and Register:
For the login and register there will be two endpoints and they needs to return error which provides message about that such as "username is already taken" or information that specifies "the success of the register or login". -
Going to home page: After registering and login the client side will request the these things: they want to show some parts of the waste goals, leaderboard and forum as button like last three row instances of them. And after clicking these the leaderboard, waste goals , forum page etc will be opened. So, to see the information about the pages in the home page , they want a endpoint that provide parts of the waste info , leaderboard, and forum.The home page endpoint needs to be written.
-
Forum page button: When person clicks to forum button the pages will be open according to these: Client side will want "x" number of posts and they will also give a last Post Id if they want new "x" number of posts when the user scrolling. The posts will be seen according to these: If it follows anybody the posts those user made will be seen with the date order( newest first) After these the other posts will be seen. The likes comments info for the posts needs to be sent also.
-
Profile part: When person click to his profile part, the profile page needs to be seen. There are two main endpoints for here. One: Get Profile Info: Basically send the profile info to the client. Second: When person tries to edit the page, they needs to send the edited info and the profile info has to be updated in the system. For the image upload, the url of the image needs to be put into the database and the image needs to be stored in cloud services. The logic can be separated for the image update etc. as different endpoint.
-
Commenting, like etc the post: For these there should be an endpoint that the new likes comments saved into the database.
-
Waste Log And Goals Part: When the person clicks to waste goals part , he or she needs to see his or her goal lists and info about them ( percentage of achievement etc.) For seeing waste button , there needs to be a endpoint that provide the information about that. When user tries to log their input, for update of them the client side will provide the information goal id and corresponding log to it etc , and we will save it, for this one there might be an endpoint.
-
For the home page part, the service functions that other endpoints uses for the other parts could be used with the different number ( 3 posts for the forum etc.)
Action Items
| # | Details | Assignee(s) | Deadline |
|---|---|---|---|
| 1 | Login and Register | Cengiz Bilal Sarı | 19.04.2025 |
| 2 | Waste log and goals part | Ahmet Mert Balcı | 19.04.2025 |
| 3 | Profile and Comment, Like etc | Ahmet Ege Tanrıverdi | 19.04.2025 |
| 4 | Forum Page | Osman Yusuf Tosun | 19.04.2025 |
| 5 | Home Page | Cengiz Bilal Sarı | 20.04.2025 |