Repository navigation
How did we work together?
Within this school course, we started out with our individual project and had to choose someone's project from our team to continue "extending" the application by adding each of our own functions, which we made in our individual projects. We choose Dish Exhange, because at the time we had to choose, application had one feature that worked in comparison to the others. It also wasn't entirely finished, like someone else's project in our team. This is the main reason we chose to work together on Dish Exchange.
We started out in dropbox to take notes and to easily document important information: https://www.dropbox.com/scl/fi/5n6978yylpmv5u8ik6c2l/Team-Dish-Exchange.paper?dl=0&rlkey=ai2qoirtd9dq3x47eoseyhi8t . It's very "raw" content-wise, because it was a temporary thing we used. It was just a place to gather all the information at the time.
We all had experience with EsLint, hence is also why we choose to use EsLint as our linter. It didn't work for everyone as good, we tried to fix it, but it took too long to figure it out so we just let it be.
We choose Prettier, because we all had experience with this formatter. For our formatter, we made a .prettierrc to configure the formatter.
As a team, we learned alot. It was very difficult, especially because we only had two weeks to work on this team project.
The first thing we messed up was the branches. I thought you could call it whatever you want and it made sense to me to give it names of the person who's going to work on it. I thought it would be easier for everyone to just know in which branch they would work in. We later learned that we had to change the names from our branches into the names of our features. I guess that makes more sense, because an outsider then also knows what's inside the branches by just looking at the name of the branch.
We didn't start with the MVC Model, but instead we just started working in our own branches. When we wanted to merge everything together, we had a lot of merge conflicts. We sat together as a team with teacher assisting us and that really helped alot. We immediately started on the MVC model, mainly Dave Dankwah, because he could do it easily and understood it the best of how it worked. Later that week he improved the MVC model and added controllers.
Whenever we made a merge, we always did it together. This way we could help each other out, look for each other code. This is also why the comments when a pull request has been made aren't the best, because we actually discussed alot offline regarding this matter.