Skip to main content

Final Contributions

As the final weeks of our semester approaches, i submit my last two pr. During these months i have learned many things and had fun doing it. Working with Github and Git was the best learning experience i had throughout the months. I also had the opportunity of researching and experimenting with open source technologies. Overall everything i learned from this course i will for sure use, for instance, using git at the workplace or use of open-source technology for other projects.

I took the time this week to review the requested changes made to one of my pull request that i had made to vscode. I managed to close two changes but i have one more change request to make before i could ask them to review it again. 

Last week my plan was to learn more about Lighthouse and implement it into our course project. After a few days of working on this issue, i came to a conclusion of using the following code as my solution:
"lighthouse-index": "lighthouse http://localhost:3000 --output-path=./index-report.report.html --view"
"lighthouse-login": "lighthouse http://localhost:3000/login.html --output-path=./login-report.report.html --view"
Once running the following scripts, Lighthouse runs through our html pages and spits our results which with the flags --output-path and --view will save the html file locally and open a tab to display the results.


After submitting my pull request, my course instructor suggested that i make a few changes. One of the changes was adding another script to run the project on the web because my script requires the project to be running. Something i missed it and did not take into consideration. After the changes were made and reviewed my code got merged into the master branch.

"lighthouse": "cross-env PORT=3000 npm-run-all -r -p server lighthouse-index"
For future projects, i will take advantage of npm scrips as it provides a way to automate boring tasks.

For my second pull request, i had the opportunity of learning about more open source technology. For the issue, i had to combine eslint with prettier and add it to the project. Also within the issue there was a request for adding eslint plugin for cypress which i followed the instructions on their Github page. I created this pull request for the issue. I'm waiting for the main contributor to review what i have done. I'm hoping to do more with this issue i resolved like adding rules and create scripts for the project.



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

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...
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