Vincent's coding journey

Travis CI is a continuous integration service that helps compile, build, test and deploy code for GitHub projects. Just to test it out I decided to add it to a repository that I was working on (Currently has no Continuous Integration bots) SenecaBlackBoardExtension . Now I have to give the bot something to do. Since SenecaBlackboardExtension is mostly JavaScript code I decided that the best starting point is to run ESLint with Travis CI. Travis CI can only be connected to a GitHub account that you own. I don't own that repository so to work around it I forked the repo so I have my version of it. With the help of David Humphrey , who was familiar with ESLint, and the ESLint and Travis user guides I was able to run ESLint with Travis in my forked repository of SenecaBlackBoardExtension. Once it worked on my forked version, in theory it should work in the main repo with little tweaks (Eg: The owner to connect his GitHub). So I made a pull request to add in the files that are n

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

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,

Based on previous blog post: here . My second pull request was a simple fix but a huge bug. It all started when I was working on my previous issue . At school, I downloaded the zip file for SenecaBlackboardExtension from GitHub and ran it on Firefox to see what we have working so far. It had an email login and the "did you know" box was taken out. It was getting near the end of class so I decided to work on the first issue at home. Once I got home I updated my forked repo and test the extension again on Firefox and... it didn't change the page and no errors were displayed. So I quickly went to check the repo to see if any new pull request was merged. There was changes but 1 of the changes was on the readme file and the other change was on the manifest file which was for icons. The change to the readme file shouldn't have affected it so I tried reverting the change in manifest but the extension still didn't change. I then used "blame" from GitHub to s

For my open source class at Seneca, we are now at a phase where we can start creating our own open source project. After both class have brainstormed brilliant ideas, 12 of the most popular ones are created. From the 12 projects, I was interested in two of them. The first one was the SenecaBlackboardExtension project because as a user I know best what could be improved. The other project that interest me was the Turn-based creative writing web app . The first issue that I created on SenecaBlackboardExtension was a great idea suggested by my professor(David Humphrey), which was to include a details/summary block to show/hide things on the site, instead of removing everything from the website. The first place I thought of using this was the Seneca Services box, since all the links in the box are important but only a couple are used most often, so I decided to add a collapsible view for the links that aren't used as often in the issue I've created.

During the Hacktoberfest month I have worked on these issues: https://github.com/theelous3/asks/issues/87 https://github.com/notepad-plus-plus/notepad-plus-plus/issues/4907 https://github.com/filerjs/filer/issues/551 https://github.com/cjlcarvalho/crazy-robots/issues/18 https://github.com/cjlcarvalho/crazy-robots/issues/20 https://github.com/cjlcarvalho/crazy-robots/issues/2 What I have learnt:       I have realized that 5 pull requests may not seem like a big number to do but to do that in a one month of time, it's more than you'd think. At first I completed an issue during the first week so things were going as planned. During the first week, I also got to learn a new programming language(Python) mostly just to understand the part that I was working on. Once I got to the second issue, I got stuck at setting up the environment, it took about 1-2 weeks and I was still getting errors while trying to build the code. That is when I decided I should push this issue of