OSD600 Release 0.2 PR 1

The time has come to start release 0.2! For this release, we start contributing to real open source projects on Github! When I read what we had to do I was excited and nervous at the same time. I never contributed to Open Source and was scared of things such as not being able to find anything I can work on, or start working on an issue then realizing I have taken on something too challenging. What I learned after my first pull request is I was wrong!

I started looking for good first issues on the up for grabs website provided by my professor. It took a lot of searching but I finally found an issue perfect for my first pull request! This repository was working on a cli application to create almost any programming language file. I looked through their issues and found this They wanted people to pick a language and do various things with it such as write a hello world and document how to create inline comments. I noticed they already did SQL but was missing PL/SQL. I already had some knowledge about PL/SQL so I felt comfortable doing this. I made a comment and told them I would like to add PL/SQL. Then I waited. After a while, there was no reply so I decided to go for it and make a PR anyways (either way I saw this is a great opportunity to practice). The set up was very easy as I already had a text editor installed on my laptop and knew the PL/SQL syntax. The code I wrote was a simple PL/SQL block that outputted hello world. Then I added some documentation on how to write inline comments in inlinecomments.txt, and other minor stuff (update read me, modify another document ect..) While I was working on my code I noticed a small typo in one of the other files, so I decided to fix that to and tell them about it. By the time I finished and made my PR they replied to my request to work on this! 

To be honest I didn't think I would have to do any research for this pull request until they replied:
While I took DBS501 at Seneca we always used the .SQL extension while working on PL/SQL. I was shocked when he asked me this. So I started to do some research and learned something I never knew before. When working in PL/SQL the extension can be .sql however, its better practice to use the .pls extension since that indicates it is a PL/SQL script. When I started working on this issue I didn't expect to learn much outside of contributing to open source. I am very happy I got to work on this because I also learned more about PL/SQL. Moral of the story: never think you know everything, there is always something new to learn!








Comments

Post a Comment

Popular posts from this blog

OSD600 Release 0.4 Part 3

Image
 This is the last blog for OSD600 and the last part of release 0.4! I am excited to be writing this as after this I will be done with everything I need to do for my classes this semester, and graduate! One issue I noticed while working on this is I did not fully understand what was needed to "port" a component from Gatsby to Next. At first, I thought everything you needed to do to port a component was in this migration guide  posted in the issue . After talking to some people on Slack I learned we must not only follow the migration guide but also convert the JavaScript code in the components to TypeScript. I have worked with Typescript before so I had an idea of how it works/what it is (it's basically JavaScript with types), but I never knew how to convert JavaScript code to TypeScript code. After doing some research I learned this process can be broken down into two simple steps: 1. Change all the .jsx files to .tsx files. 2. Add types to all the variables made. Eg. func
Read more

OSD600 Lab 5

Image
 This week we learned about rebasing in Git! Rebasing is basically taking multiple commits and "grouping" or "moving" them into one commit. Before I started the lab I did the walkthrough on the OSD600 GitHub Wiki. At first, I struggled with it (kept getting errors when running git rebase master -i). Then I decided to start over again and I noticed the first time I forgot to commit some files on the refactor branch. I am happy I did this first because it made the lab go very smoothly.  Before I started the lab I took a look at my code and wrote down the improvements I was planning to make. I decided to do these 3 things: change my regular expression variable from a let to a const, remove an array I never used, and update some functions to use the ES6 arrow syntax. It's been a while since I used arrow functions so I used this resource to guide me Every time I added and tested a feature I did a git commit. One improvement that caused an error was when I updated som
Read more

Release 0.3 PR2

Image
  For release 3 we have to make 2 PR's. The first one must be for the  Telesope project  and the second one must be for an external project. These PR's must "build up" from the PR's we did for release 0.2. This blog post will highlight working on the PR for Telescope. When I started this the first place I went was to the issues page on the Telescope repository. I saw there were some tests that needed to be written and were interested in taking on one of these issues. These were more complex than the test I wrote for the first part of 0.3 so  I saw it as a good opportunity to improve my skill. I asked in Slack for some advice on what to do and was given this idea from David: This seemed like a good test to write (challenging but something I can figure out) so I made an issue for it and started working! When I first wrote the test everything looked fine but it kept on failing. At first, I thought that's good, if we pass an invalid date shouldn't the test fa
Read more