DPS909 Release 0.3 PR3

For my third pull request in release 0.3 I had a tough time searching for an issue for an external project that I wanted to work on. After days of searching I finally landed on this project. The issue that I found is upgrading enums to enum classes. I found this interesting because I worked on enums before but I never heard of a enum class, so it was new to me as well. As always I downloaded the code to test what it can do before messing with the code. I followed the README to setup my windows environment to compile, build and run the code. I got to compile the code however I couldn't get pass the build phase. At this point, the best option is probably to move on to a different project but I didn't want to let go of such an interesting issue/enhancement. So I went back to the README and see if I have other options, it seems Linux/MacOS have less work to do building this project. I wanted to try using Macs to build this but I don't have any apple products. Then it hit me, I remember there are a few Macs at school that I could use but because of it's limited quantity, it would be hard for me to find an available one. Once I finally got my hands on a Mac, compiling, building and running the project went as smooth as I thought.

Comments

Post a Comment

Popular posts from this blog

My third Hacktoberfest 2018 Journey

This issue I created was suggested by a nice guy(Nate) who already finished 5 PR's. The idea was to increase the performance of a robot program. Instead of using the size method, a global variable would be used to keep track of the remaining robots for a quicker comparison when needed. This program was in C++ which made it very easy for me to read since that is one of my strength. The owner of the repo later told me that he didn't want to use global variables.
Read more

Helping Mozilla firefox with enabling ESLint

Image
It was an amazing experience contributing to Mozilla Firefox. The bug that I worked on: here . For new developers to help with enabling ESLint with FireFox here are the steps that I took ( Window user ) assuming you already have a bug assigned to you: Follow Mozilla Build to download and get the "Required tools" and stop at "Getting the source" Download Mercurial . Continue with Getting the Source and stop at "Build FireFox!" it's not really needed when fixing ESLint bugs and saves some time. Remove your <directory path> from `.eslintignore`. Run `./mach eslint --fix <directory path>` this will run ESLint only for the specific directory you are fixing. Note: I was told to commit 2 versions: An automatic change version and a manual change version.      6.  So at this point I did `hg commit -m "Enable ESLint for <directory path> (automatic changes)"` Since I was told I needed 2 commits I wanted to push my
Read more

Contributing to 2048 Repo cont'd

GitHub Repo: 2048 Previously, when I was working on this repository it turns out my code format was not consistent with what they had. I've noticed that they have a .clang-format file which means there should be a way for me to run it and auto format my code. After searching, I have found a couple of online formatters. When I used the online formatters it either spits back the same code format or it loads until timeout, either way I don't get what I am trying to do. I went back to searching for clang-formats and I came across a Visual Studio Code extension that allows me to use the .clang-format file. After running the clang-format on the source files, compiling errors start to arise from the .clang-format file which I have posted an issue on. After trying to fix a few of the errors the owner of the repo believes the error could be related to the VSCode extension. Apparently, they were using npm to run the clang-format file. Maybe I should have asked how they did the forma
Read more