Release V0.3 Part 2

Internal Project Contribution

In the past and currently, I have worked on several issues within the Telescope community. At first I was worried about understanding other peoples code. However, after looking at a few issues and spending some time on Telescopes repository, I noticed that I could contribute to some of the issues that our community was facing. In total, I worked on three different issues all ranging from different skill levels, the easiest being the documentation update. You can check out the changes that were implemented here. In order to update the documentation, I had to read up on all the different types of logging. I excluded the unnecessary information from Telescopes documentation to accentuate the important details about how to implement the logger.

The documentation update got merged fairly quickly, this gave me a sense of relief since I was worried that I would not be able to get a commit in before the due date. Completing the required pull requests for Release v0.3 early, allowed me to tackle bigger challenges like implementing a test. I have never implemented a test, so this was a never racking experience for me. While researching about the options to solve this issue I decided to resolve, I gained some exposure to Jest. Jest is a JavaScript testing framework maintained by Facebook. I have never worked with Jest before it was very interesting to see how it worked.

Another issue that I decided to tackle was front end CSS. Currently, I am still trying to decipher what triggers the CSS change and will have to dive deeper.  The mystery continues...

 




Comments

Post a Comment

Popular posts from this blog

Working with others

     This week our course was given the task of creating a cli command, which included our code being reviewed by one of my classmates. Initially, this gave me some anxiety as sharing my work with others is not my strongest suit. Nonetheless, I created a post asking if anyone was looking for a partner and Michael Appeared.      It turns out that having someone look over my work was much less scary than I had initially anticipated. Working with Michael was actually fun, and having the opportunity to look over someone else's work was a great learning experience for me.       With another pair of eyes looking at my code, Michael noticed errors and instructions that I was not addressing. Some instructions I had forgot to mention include the fact that my program requires bash. It did not occur to me that most of us live in a Windows Operating System. Another missing component was my Blog link in my READme. I had forgotten to include a link to my blog! As soon as Michael notified me he w
Read more

The Progress

This week I decided on a repository to work on, the telescope repository. I was excited since this was a front end development issue. I had never created my own component before, however, I have some prior experience using React. I started by creating a bottomBar component and locating where I should add this component. I located the PageBase.js, the mobile application interface, and added the component to the bottom of the page. I started by creating a div with a red background to make sure I was on the right track. since it has been a couple months that I have not worked with React, I started with the most basic tasks, such as, creating a react component, a  div element, and rendering the component I made.     After confirming that I did not break anything, I started designing the layout of the desired BottomBar. The idea was created by  agarcia-caicedo,   proposed a bottom app bar t o improve mobile usability. If you're curious on the original idea you can check out his 
Read more

We are off! V0.1

Initial Release V0.1  Our first Assignment was to create a command-line tool to check and report dead links in a file. Status code 200 would be considered "Good", 400 and 404 is "Bad", and all other status codes are considered "Unknown." My first experience creating a release was nerve racking. With no instructions on how to approach this problem, I started to brain storm ideas, and eventually started questioning my abilities. Inevitability, I chose to do my assignment in bash since it would allow me to colour my code, as well as create a command line tool. Overall, the first assignment was fairly simple to use. Simply clone or fork the repository, open up bash, and run the command. Command : ./cliCommand <filename> NOTE: This project will need Bash installed on your machine. Mac OS has bash built in, however, Windows OS may need to install Bash. Please feel free to play with codes, if you have a crazy idea, then pull request :) Usage and Features Us
Read more