OSD600 Lab 6

This week we started to get familiar with Telescope a tool made by students of OSD 600 to track blogs written for Senecas Open Source class. The first task of this week's lab was to set up telescope and get it to run on our local machine. I first read the envirenmet-setup.md file and decided I will use the docker and docker-compose method. After I forked and cloned the repository I downloaded docker decktop (this comes with docker and docker-compose) then followed the steps to run it. I did run into some minor issues when trying to run it, but was able to figure it out! 

After I got that working I started the second part of lab 6. For this part, we had to modify our link checker to search for links in the last 10 telescope posts. To be honest, at first, I had no idea how to do this. But then I took a minute to think about it and start writing some code (It's easier for me to visualize). Eventually, I figured it out! I used fetch() to grab the JSON data from http://localhost:3000/posts (the telescope REST API)

 then I went through that array and used fetch() again to fetch() each blog post (eg  http://localhost:3000/posts/8868d79346). I then used response.html to get the HTML of each blog post (I didn't know about that before, had to do some research). After that, I stored the HTML of every post into one text file.  From there I was able to use my existing code to go through the file and check all the links. I am really happy we did this lab because by doing it I discovered a flaw in my link checker app. The first time I ran it I was getting many links (3000+) I was not sure if something was wrong or if that's expected. I talked to David about it and realized I never took out duplicates from the array. After I did that the size went down a lot!  Besides that modification, there were not many changes to my code,  everything was minor (adding a --telescope option and writing a new function for that use case). The existing code I had written in the past worked well. 


Finally, I uploaded the files I had to write to finish this lab to this gist. Overall, this lab went pretty well, and I am looking forward to the next lab and starting to work on Telescope!












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