Vincent's coding journey

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

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