This repository was archived by the owner on Jun 5, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Backlog
SARUXSARU edited this page Jun 4, 2023
·
34 revisions
- This week we have been looking for ideas for our project. We focused on making it possible for us to implement all its functionalities and we provided ideas for the environment for its implementation. We also started Github repository where we saved our ideas and where we will share our whole project in future.
- This week we summarized our ideas and chose the one that seemed the most interesting. We also chose the environment for the frontend, backend and database. We also shared the work for which part of app who will be developing it.
- This week we started implementing our application. We created a login/registration page and connected the database with the backend. We can read and write new data to it. We have also implemented a new user registration/login through the application page and saving it to our database.
- This week we started creating function for adding new events to aour app, in which users will can take part. We made site for it and "easy" way ( we have to make it better in future ) for adding new event. We also added information about strength of the password during registration on page.
- This week we repaired logging into our application and we added logging out function. We also added functionary for creating events with description of it and showing them on user page. We can also adding and deleting registered in app users to existing events.
- We have already added expenses page to our app and we also can adding particular expenses with information who, when, for what paid ( user can choose expense cstegory from list ). We have to add information about people for who expense was made, in next week.
- We add functionality of sharing expenses beetween event members when we adding new expense to event. We also create project of the logo and favicon.
- We we add information about who how much money spend in each expense. We also add favicon and app logo to website, cleaned up our code to make it easier to read/work and we write all test for the parts of API which don't need a token.
- This week we added validation to prevent adding our self to the exisiting event. We also created view of all events in which user take part ( earlier we could see only these events which we created ) it means we can also see events in which we are not owner but member. We checked too how how our application works on mobile device and write api tests for geting existing events/expenses/(adding/deleting member to/from event).
- We add opurtinity to open our app on mobile device and we can also use all our app functionality like login/register/adding events etc. We also started creating end of event endpoint. For today we can see on the backend console end of event calculation about who have to pay to who and how much money. We also fixed some small bugs like bad response code or data founded during tests. In test section we repaired tests about deleting people from event.
- This week we added to our app page with information about finished event with calculated receivables for each event member. We also changed buttons with words for icon buttons to make more clear view of our app. We also added animation of loading page to made waiting time for respone more pleasing to the eye. We also writed test for archived events and for future endpoints finish/summary of event and PUT method for change information about existing expense.
- In this week we focused on ending summary endpoint. Each user which have to pay to other member of the event can click button which mean he paid money, when he did it person which should get money can confirm this operation whats mean delete information about receivable from data base. We also written tests of it, repaired GET summary tests and GET finish test.