OSD600- Release 0.4 Part 1

 The semester is almost over and we have one more release! For Release 0.4 we must top everything we have done before in the class! Sounds challenging but fun! I first read the assignment and saw the ideas our professor gave us. I decided I want to work on Telescope again. What drew me to Telescope was the community. They were all very nice, and I enjoyed working with them last time, so why not work with them again!

I went on Slack and let them know I am interested in working on Telescope again, and asked if there is anything I can do. I was told to look at this pinned issue. They are currently porting GastbyJs code to Next.js code and can use some help porting the modules. I decided to do Login/, To be honest, I have no idea how to do this (although I haven't read any of the documentation provided yet) but I'm really not worried as I know there is a large community of people, and great resources to go to to help me accomplish this. Another great thing about this is I will learn something new. My plan for this is to read the provided documentation and see if I can find any modules in Telescope that were already ported from GastbyJs code to Next.js, then start writing code. The main goal of this PR is to figure out how to port the code, do it correctly, and get it merged! I'm sure with hard work, I will be able to accomplish this!


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