Skip to main content

Taking on new technology

In my last week's blog, I talked about the two objectives I would take on during November. In the middle of working on the contributions, I decided to change my issue for the internal open source project. I'm hoping to continue with this issue for next pull request I have to submit for my course.

As you know, the external open source project I chose to contribute to was vscode. In the beginning, when i saw this issue, i thought this would be an uncomplicated and straightforward issue to work on within a big open source project. Before i forked the clown, i took a good look at the documents they had to just get a sense of how to contribute to the project and do the simple tasks of running and testing. After cloning, i had an issue running the project, this is where i spent some good time reading the documentation again, but i was just having a hard time running the project. I managed to get it running after a few reads. Thanks to another contributor i had a hint of where to start the implementation of the issue. When i opened the code base i was overwhelmed with all files and lines of code. I spent a few hours trying to understand what was going on. With suggestions from other contributors, i made the changes. But i wasn't fully done, i had to apply a background color to the feature i was implementing and again i couldn't figure it out for a long time. After a few days of researching and trying to figure out a way, i asked for help from a contributor. I was directed to a way of doing the background color and i tested around to see what would be the best. After some trial and error of the colors, i figured i would just implement a way i think was better than what was suggested. I created this pull request and am waiting for feedback on how i did the implementation. Overall this wasn't like what i had expected. I found it very difficult to implement the feature and getting a grasp of the code.


For the internal open source project, i decided to help another classmate with their feature. The issue was raised by the developer of the feature and he needed help writing the testing part of his feature so i decided to help him. For the telescope project, it was decided that jest would be the technology used for writing the testing portion. Personally, i had never heard or worked with jest so it was a good experience and exposure to something new. With the help of the developer and reading the docs, i was able to write two test cases to test the functionality of the feature. After raising this pull request, i had classmates review the code. One classmate suggested a change to my code which i agreed to and i definitely did miss.

Comments

Post a Comment

Popular posts from this blog

Whiteboard Application: Built with Open Source Projects

I just took my first steps into the open source world and it was amazing. As my first project, I built a note taking application with the help of some open source projects and Github. I’m going to admit, I was a bit scared at first because I hadn’t touched web development in months so I was I rusty in Javascript and other web technologies. Thanks to my instructor, I was able to set-up everything on Github with ease and execute git commands that I had forgotten. All in all it was a good experience and was nice to get back into coding after a long break from it. Whiteboard Application The point of this application is to allow users to takes notes on a webpage. There are also features such as saving what you have written on the whiteboard or clearing the whiteboard all at once. The application was built using the following open source projects: ·          Filer ·          PaperCSS ·   ...
Post a Comment
Read more

Using Lighthouse with Node CLI

Last week in my blog i mentioned working on integrating Lighthouse CI into our course project . The goal was to provide a tool for contributors working on the front-end side of the project. With lighthouse, our contributors could run some diagnostics test to know which parts of the front-end could be improved upon. So for the last week, I have been reading documentation and blogs/articles for lighthouse ci. One of the things i picked up was that for a future project i could use lighthouse ci and integrate it with my server, and also i can use Github Actions to automatically run diagnostics and produce reports. But this wasn't the solution we needed for our course project. So i came across the CLI documents . With the Lighthouse CLI, I would be able to set up it up and test the files locally. Using npm i installed the API: npm install -g @lhci/cli Afterward, i used collect the run the diagnostics tests and store lighthouse reports in the .lighthouseci/ folder. Usi...
Post a Comment
Read more