Week of Lab 1 of Open source world

 Hey PC readers:

 

Welcome back. So this week we were given a task. A task to create a CLI tool to check the URLs and display if they are working or not, or just unknown. So to gain experience and of course, grades I created that in my release 0.1, more info can be found here. To enhance the tool, Prof. Humphd asked us to work with some of the peers in the class to get some useful reviews and suggestions to make our app better.

 I started Lab 1 requirements by first completing my release 0.1 work with its mandatory requirements and completing 2 of its optional requirements. Then I went on to the Slack to find my partner to review for Lab 1. Fortunately, there were many students working on Node.js and I got one instantly like it was fate lol. She was also looking for partner just then for Node.js.  We let each other know the timeline for our work completion, so that we are ready to review once it is done. So I tested and reviewed her code, it was working. There were some errors which I was working on to mention in the code, but another peer posted before me. So I went on to comment about remaining errors I found in readMe and code. Link to issues I found is here.

It was a good practice to get someone review my code. I did my first PR and review on github. Then I fixed them and merged them into my master. It was my first time getting reviewed at Github at all. She gave some useful insights which I took and fixed. Most of the issues were in my readMe, I was thinking that it was clear but maybe I did it, I knew what was going on, not the other tester. So it made sense when commented that. Also, she recommended to use the html file for the link which I will work on in the upcoming days. I fixed all the other issues. Link to my issues are here.

Well, all in all, it was a very good experience for me to communicate with new peers and work with them on Slack, and Github. Learning more and more every week. 

Thanks for reading, see you in my next blog.

PC

Release 0.1 or the first ever release blog

 Hey PC readers:

Welcome back to my blog. So, for the first two weeks of the Fall sem in Open source, we were assigned with a release called 0.1 for our first Open source commits and project repos. We were asked to create a tool for release 0.1, specifically a CLI / command line interface tool which will go through a list of URLs and define if the URL is good or not, if it is working or not. 

So my tool will display " Good" in green, if it is working. And if not working, then it will show "bad" in red color. Third display option is of URL which are of unknown status, they will be displayed as"Unknown" in grey. All of these displays will be accompanied by the request status code, like 200, 400 , 404 , or any other status code; with the URL itself. So cool, right? This was one of the additional feature that I chose to use the color, from a list of additional feature list to choose from.

I also added the additional feature of checking the version of the tool. Personally, I always juggle between -v, -V, or --version(dont judge, haha), so I enabled all of these to check the version of my tool. 

I was very excited by the choice given by the Prof. Humphrey to choose any programming language to make this tool. That was fun, it will give us the chance to work on the language which we want to work in future. I highly appreciate this kind of freedom to choose and work on your own things.

 I saw many of the members in the slack were using fetch to fetch the URLs, so I wanted to try something new, so I used Axios in my project to fetch the requests. I also wanted to experience new with colors, hence I used colors instead of chalks(which I checked out with many of my peers, thank you). So, anyone can review my code by cloning my repo and using the command "npm install -g https://github.com/chawlapalak/Url-Inspector   "   if it is in master, if it is still in develop branch and getting reviewed by my main reviewer who is assigned for reviewing i.e. Muskan Shinh  -   @shinh18 (github)  then you would need to follow these steps: 

Step 1: git clone  "path" you can copy from my repo
step 2: git checkout develop
step 3: npm install -g ./
step 4: url-inspector -f test.txt

Here is a snippet of my tool running with the command:

 

 So, feel free to drop by my repo and review it, all feedbacks are appreciated. 

https://github.com/chawlapalak/Url-Inspector 

 

Thank you for reading it. :D See you in my next blog.

Intro to Open Source

 Hi everyone, I am Palak Chawla, a student of Bachelors of Software Development Degree in Seneca College. I am a little bit more than halfway through my degree. I wanted to learn something new and useful for my career. Hence, I left my job as a Mobile software Tester in India and came to learn development here in Seneca. After a while, I felt I needed to take a very useful course for my professional option which will actually help me in my professional life, and not do it for just the sake of doing it. Fortunately, this course DPS909 which is about Open Source came highly recommended by my friends. And I believe if I want to work as a Developer, I need to start working more with the GitHub and start my journey of working with the community with my inputs in code and other things.

 I am residing in Toronto , Canada right now. I am taking this course with online platform teaching medium. To be honest, the first week was really hectic for me, as I was not sure what to do, when to do, how to do. It was really overwhelming for me as every course is spread on different platforms other than Blackboard this semester. It was hard for me to keep track of deadlines and classes etc. But I am working on it and making a list of deadline due dates, class links etc in this week.

 I am hoping to gain some new confidence in myself with the open source community. I do feel like I should know more about coding and trending technology, different communities such as this one. I came from a testing background, and things are very different in that stream. This will be a good start for me to start as a fresher in the open source community, even as a blogger. This is my very first blog of life-time. Thank you for making me do it. It feels good. I am not sure what kind of repositories I want to work on, I want to explore and go with my excitement flow. I am hoping something with React maybe, but I am not sure. I want to work on React in my upcoming years, and I am trying to start working on my skills.

I went to weekly trending, and found react-challenge  really interesting. It is based on JavaScript, and I was planning on start practising competitive programming on JavaScript and React and this really caught my eye. 

I would try my best to write my weekly blog. It is really fun.