Release 0.3 Internal PR

    One of the Pull Request for Release 0.3 was to work on an Issue for Telescope, knowing that I had already done an issue on Telescope during Release 0.2, I was happy to make another contribution to the project. This time, I decided to work on the notification favicon.

    At first, I thought it was just a simple task of creating a version of the favicon with a red dot on the top right corner and then changing the favicon from a component, but it was a lot more than I bargained for. There are several things that need to be done in order to get this feature working, the state of the current window's visibility must be determined first in order to execute the hook that changes the favicon. Once that is done, you will have to obtain the id value of the previous app page's top post and compare it to the current state's top post's id. When all the conditions are met, the favicon of the website should switch to the badged version until the window is visible again.

    All this work could not have been done by me alone for I had never learned about React Hooks as well as it's States, Professor Humphrey was kind enough to help me throughout the entirety of this Issue. He provided me with the Hook that allows the favicon to be changed when the app's visibility is false, as well as SWR options to handle unfocused data refresh.

    Before help was received I was convinced that the SEO component, where they render the head elements will be where I put my code, for that was the only method for changing the favicon that I know of at the time. I was basically on a wild goose chase until I received help from the professor, now I know you can access the favicon using hooks and all that had to be done was locate the functions inside the component that renders the post, and access the data.
    



    In this Pull Request I learned tons of things that I had never touched before, things like editing SVG files, React Hooks, React State, etc. I really appreciate David's guidance on this topic, this makes me want to get into more repositories with issues that handle the above subjects.

Comments

Post a Comment

Popular posts from this blog

Lab 2 Blog

     Today I contributed to another user's project on GitHub , I wanted to work on a feature where it counts how many times each type of HTTP status code as well as URLs in total has been checked, and then display it as a result section of the output.      First I sent out an Issue on his repository regarding what I wanted to do and proposed to work on it myself. After I finished adding my feature, I issued a pull request to the person's repository as I wait for feedback.      During the making of the Result Counter feature, I started by creating variables to hold all the counters and display messages. Then, I put the counters inside the loop that determines the status of the URLs, counting each and every time the if statement was valid. The total amount of URLs are added each time the loop had completed. One major problem I came across while making this feature was the fact that the result message were displayed before the list of URLs were outputted, the only way for me to
Read more

Lab 4 Blog

     This week's lab consisted of going to a new user's repository that we haven't worked on before, and add a new feature called "Ignore URL Patterns" onto their Release 0.1 repository. This feature will be activated after a new argument '--ignore' had been received, containing the ignore argument will allow the CLI tool to read two files in order: the file that contains the list of URLs that will be ignored by the link checker, and the argument after that will be the targeted file to scan.     I created an Issue on another person's Repository , and once I got permission to work on the issue, I Forked the repository into my own and cloned that forked repository into my local machine. I ran through the code and got a better understanding of how the code works before working to add the feature in.     After the feature had been completed, I contacted the owner of the project through the issue that was opened to let him know that I had finished the fea
Read more

Release 0.4

     The final assignment is finally here, it is almost time to say goodbye to this semester. Throughout the semester, we've done many different things and was involved in several open-source projects where we learned and overcame problems. This is the best course to explore Github and get some hands-on experience with programming, the open-source community is vast and filled with professionals that you can work with as well as learn from.     For the final assessment, I'd like to work on a feature that I've never touched before to prove that I did indeed grow as a programmer from taking this course. I decided to work on a repository that had started contributing to since Release 0.2, qasong . I picked this because they are a project that is near launch and I grew to like their team's effort as well as what they do, I definitely learned a lot more about React by contributing.      I am currently contemplating on taking an old issue that was never taken since September,
Read more