DPS909 - Mamadou Diallo

This is the final iteration for DPS909.  For part 4 of this iteration, as you may have noticed from my previous contributions. I like to participate with repo's related to math.  This reposition that I found triangle-calculator  is a tool that helps calculate certain values based on user input about a triangle.  I think I caught the owner off-guard as he wasn't expecting for anyone to help with his issue. He was looking to get his tool tested. His code wasn't lacked functions/was not refactored so I couldn't really test his functions BUT I did manage to find bugs in his code. As he had asked me to create issues for him to fix those issues. I fixed minor issues for him and offered to help him with the bigger issues(if he was okay with me doing so).  His code really showed me the importance of commenting/refactoring code as while I was going through his code understanding the logic was slightly tedious.  I tried to use googles testing tool but gave up after a short while

This is the final iteration for DPS909.  For part 1 and 2 of this last deliverable, I wanted to apply tools that I've learned in the second half of this class. In my previous labs we learned to use code formatters, linters and also used tools to test our code.  I wanted to translate the tools that we recently learned to use, I chose to work on dev-jot as there was many tools that could still be added to the project.  Although this felt similar to my previous labs, I'm still not too accustomed with visual studio code & javascript. I still managed to learn quite a bit.  1. Using the terminal IN visual code is EXTREMELY helpful, instead of having to tab between my windows command line & vs code.  2. VS code is a very friendly platform to implement/add plugins.  3. Understood the package.json nomenclature slightly better.  For this lab for formatting and linting, I used ESlint and prettier. This was fun for me as when working on telescope with my first PR I had issues with

  This week the goal for our lab was to make our tool downloadable for your average day users.  I found myself to be lucky as the my choice for continuous integration was inline with this currents week lab. My project in java and I had opted to use maven to implement my CI. In this weeks lab, I took the opportunity to properly fix the architecture of my project. I removed obsolete folders & moved on to lab 9.   Although I started using maven in the previous lab, I still had some issues hosting my tool. As maven files were imported after the initial creation of my project, I found myself to be missing critical components for my deployment. My pom.xml file was not tailored properly and my settings.xml was non-existent. This part was a bit tedious as I knew if I didn't write in the proper credentials, my deployment would fail.  Once everything was ready to go, my initial deployment failed. After a bit of research I realized that I had never push my public keys to any hosting platf

This weeks goal was to test our code that was written.  To begin I had my usual issue with git rebase... Lines of code that I thought shouldn't appear was appearing. From the very start of this lab I took the liberty of removing duplicate code and commiting to my master in hopes that it doesn't appear anymore for future labs. Once my code was clean and up to date, I began to create test cases using jUnit. Due to not having tested in JUnit in a very long time I had to refresh get some refreshers. JUnit testing made me realize that maybe there was more functions that I could've refactored as I only had 2 functions not including my main to test.  In regards to adding a coverage tool, luckily I didn't have to use any external tool. Intellij has a built in coverage tool that is able to generate its own coverage report. To run it one must simply run the code with coverage.  In regards to my Continuous Integration, I decided to go with maven. This was my first time using any s

For this release the goal was to have two pull request. I had to make an internal contribution to telescope and an external contribution which I made to a Data Structure repo that I've found during hacktoberfest. For telescope I decided to go and fix issue #1278 (Add docs on how to debug the backend) . I chose this issue because I myself was not comfortable with VS code and had no knowledge on how to use it. I thought that creating a doc file would be somewhat easy but what I didn't realize was that keeping the same "Syntax" as other documents would be challenging.  My PR can be found here :  Fix for issue #1278 : Created debugging file For my external pull request I actually wanted to find something new, I was looking to code something in java but found that there was lots of spam after going through multiple pages of open issues. After unsuccessfully finding any decent repo that I could contribute too, I decided to go back to release 0.2, I initially wanted to work

  For this lab the goal was to analyze my code using external tools.  Although there wasn't much coding involved, this was good a good learning experience as I did not know that such tools to format and scan for bugs existed. Using google java format I was able to format my code, other than improper spaces my code didn't need much modifications. As for the linter I used SpotBugs, which surprisingly didn't return any errors. Through out this lab my only issue was with Intellij, my plugins weren't installing properly and my only fix to that was to upgrade from Intellij community to the ultimate edition Additionally I had issues with git when trying to squash my commits. For some reason I initially my git rebase command was telling me I was already up to date, then tried to rebase my current branch to master which didn't give me any squash option as seen in the screenshot below.  After doing that I had pushed my commits and could see duplicate commits for the same code