Jason Jiang

    The final Pull Request for Hacktoberfest is here and I decided to look for an issue that is about front-end creations, just like my previous Pull Request . I found a repository named Artistify , which was suggested by a fellow student Jasper Mui for he had worked on that same repository for his final Pull Request.      Artistify  is a web app that can pull music videos from youtube and allow the users to create their own list of songs and play them in the queue order. The Issue  requested for buttons on the queue cards to allow change for the position in the queue of hovered queue cards, moving the current card up or down the queued list. This feature was needed in case the already implemented drag and drop function fails to function, it is a good alternate option to move queue cards.     To get started with the new feature, first I had to gain a general sense of how the web app manages queue lists in the front-end. I was able to get a good idea of how to move the cards using th

    For the third Pull Request , I decided to work on the Repository made by OSD students present and past. The Telescope is an app that displays and updates all the students at OSD's blog posts in chronological order, I thought since I was working on CSS and HTML for my second pull request at Hacktoberfest, I may understand the front-end parts of the app better.     I picked up an Issue on creating User Experience for when errors occur in terms of displaying the blog posts. There were three specific situations that David Humphrey, our professor, mentioned:       - When the post fails to load      - When the post is still loading      - When the loading for the entire timeline fails          In order to get started on the issue, I had to go through various different kinds of installation to allow the code to run locally. Setting up  Elasticsearch and Redis Server pre-requisites took longer than expected, but thanks to classmate  Tony Vu 's reply, I was able to run everything

     For my second Hacktoberfest pull request , I found an issue on a repository for Health Assistant Client , it was a relatively new repository for it was only at the starting phases in terms of front-end. I thought that this would make a good warm-up for Javascript front-end programming because I plan to work on more front-end things for the rest of the Hacktoberfest.     The issue requested a Navigation Bar for the web app that serves as the base Navbar design. The Navbar will have an icon on the left side and four buttons on the right that will hold hyperlink references to other paths of the site, with the contact button being an actual button element.     I had almost completely forgotten how to create Navbars using HTML, but thanks to a tutorial provided by the repository's owner, I could finish it with much ease. There wasn't anything too challenging other than the fact that the web design courses we took we made mostly with React or other Javascript frameworks, but fo

     Lab 5 of the OSD555 course had assigned us the task of cleaning up and organizing our project's code. We were instructed to reduce the amount of unneeded code by removing any global or unused variables, make variable names easier to understand, and refactor any repeated codes that exist within the project. We utilized the rebase command to merge with the main branch nicely.     The lab this time is meant to have us learn how to use the git command 'rebase', it is a command that allows multiple commits done under one section/branch to be committed as one single action. This command will come in handy when making multiple fixes and changes that are under the same category, and allow for a clean commit history on the repository.     I found a duplicated code running for the file reading operation merged from Lab 4's issue, and reduces it to only one by making the first file reading operation conditional, but pass in the parameters as nullptr to prevent any bugs.    

     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

     Hacktoberfest has started! This is the first week of the event, and I've found a Repository that maintains a list of algorithms and data structure implementations featuring many different types of languages. There were already around 60 contributors at that time.       I chose an Issue that was still open, which was to implement Bin-Sort in C#. I've never done C# coding, but I heard it was similar to Java, so I gave it a go. While I waited for my request to work on the issue to be accepted, I searched up on how to work with codes in C#. As expected, it was similar to Java where the functions and the Main() function are located under the same class scope, the only difference to me was some keywords and function names.       After my request to take on the issue was approved by the assignee, I started to work on the bucket sort function. The function takes in an array, as well as the size of the passed array as n, after determining if the array is empty, bins of the List&l

     This time for our Lab 3, we were assigned to add two features into the CLI tool project that we worked on from Release 0.1. We have to first send an issue to the repository, and then close the issue after merging the issued branch with the original one.      The first feature that I decided to add to my program was to add '--good', '--bad', and '--all' arguments to the command-line tool, this feature will allow the user to filter out the resulting URLs according to the arguments that are present. I made sure that all the arguments can be applied at the same time. If the user wished to see both good and bad arguments, then all they had to do is include both arguments into the command. Additionally, the arguments can be put in any order of which it is entered. Meaning that it will read the file location correctly no matter which position of the arguments it is in.     As the first feature went smoothly, the second feature wasn't completed as fast. The s

     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