Release 0.4 : The End (of OSD600)

-

This will be my last post written for my OSD600 course, after that, every post will be about my own journey in programming. And so I wanted to say that this course, out of all the classes I've taken so far in Seneca College for my program (CPA), is by far the absolute best course I've had in the school. The topics it covers, the knowledge it teaches, and the practicality of it is just exceptional. I've learnt so much from this course, from both the professor and my own, and that's thanks to Prof. David Humphrey's mentoring. He not only taught us how to use GitHub, make pull requests, and use Git, which I should mention is one of the most well taught guides on how to use it and I recommend anyone to watch his recorded lectures on his YouTube channel, but he also taught us how to go out on our own and expand our knowledge through the beauty of Open Source Programming. With this newfound knowledge I've acquired from the class, I'm much more confident and eager to continue to grow as a programmer and as a contributor in the open source community. My only regret is that my work ethics kind of fell of towards the end of the semester and I wasn't able to or didn't give my full 100% effort in the final assignments. Though I won't let that hold me back from the things I did learn from the rest of the course.

There's so much more I could say about the outstanding quality of the course but I'm sure you can hear it from the rest of my peers taking the same course on Telescope where you can read about their blogs.

So back to the main topic, Release 0.4! I've finished all that I could before the submission date (which shout out to Prof. H who gave me an extension) And I'm a bit disappointed since I wasn't able to complete one component that I set out to port for telescope. But I want to talk about the efforts that I did put into my attempt.

Dynamic Image

The DynamicImage component was much more complicated then when I thought it was when I first started trying to port this component. Especially compared to the other 2 components that I worked on. DynamicImage is used in the landing page of telescope to present randomised splash photos taken from a website using an API. This component is initially coded in a gatsby opiniated method using gatsby components and graphql to query data. This makes porting it to Next much more complicated since data fetching compared to Gatsby is a whole another topic that I tried to learn in a weekend and failed to. But that's not to say I didn't learn anything, I somewhat figured out how graphql works with gatsby and how Telescope queries images for the component, and I tried my best to figure out how to convert it to Next Js.

The Gatsby front end included a file called gatsby-node.js that fetches the splash images used in the Dynamic Image component, so that was an extra component to port.

This was a great reference in understanding how to implement graphql in Next Js


The original Dynamic Image Gatsby component used other components such as StaticQuery and graphql from the gatsby module. The 'graphql' module used to code GraphQL queries was easy to replace, using the apollo-server-micro module commonly used as a substitute. But the static query was something that had to be rebuilt when porting to next js, since it queried data much differently in its Gatsby counterpart.

The Image component used in the current front end is also taken from the gatsby/image module, Next JS has its own image that the migration guide recommended to change to, but the props are different to since the gatsby image component worked in conjunction with the StaticQuery component

Safe to say this wasn't a topic to be crammed in a weekend and so as much progress as I tried to make, it was still way out of my reach.

BackToTopButton & GitHubContributorCard

The other two components thankfully were simpler to port and mostly consisted of dependencies added in the package json and converting the components to typescript/tsx. But I know the whole migration process is a slow and gradual one that requires the cooperation of with the open source community of the repo. So there's still lots still left to do. 


I wish I hadn't ended my final assignment in OSD600 this way, but I know that my work in open source doesn't end here, in fact it pretty much starts here. Even if I hadn't finished the work I set out to do now (I mean my PRs are still yet to be reviewed! Lots to followup still) I'm still looking forward to contributing to more open source repos starting with Telescope.

The telescope slack page


Thanks for reading

Comments

Post a Comment

Popular posts from this blog

Release 0.3 : Telescope and The Quest for Infinity.... Scroll

-
Image
Welcome adventurers, sit down while I tell a little story of a brave programmer who slayed an issue so boldly, his PR request broke a record all time high of 57 comments. Alright so Release 0.3. Got it done right on time, just by the hair... I took on an issue on Telescope that was to add paging functionality to the search results, which also related to the another issue which is to enable infinite scrolling to the same component. Prior to this, humphd (our valiant maintainer and professor, whos been reviewing like a million PRs for the past few days.) has already added the SWR react hook to implement the same feature but on the home page feed. So I used that as a reference point. Issue #1222 I started work on the issue and first tried to implement the swr react hook with the current search components we had. This was confusing and tricky since with a search page we want to wait for the parameters for the search to be entered and then wait for the user to click the search button befor
Read more

Introduction

-
Hi everyone, welcome to my blog. My name is Joel Azwar and I'm a student/amateur programmer studying Computer Programming and Analysis in Seneca College in Toronto. I've taken up an Open Source Development course this semester and this blog is going to be dedicated to my ventures into open source technology and the progress that comes along with learning about it. So it's going to be my personal developer journal.  Open Source technology is something that's always intrigued me about the field of programming. I think it's quite fascinating how programmers all around the world can combine each other's efforts to improve, fix, or change something very drastically. Regardless of what they do, it helps advance the project one way or another which is a positive all around.  The scale of it is also quite captivating. There are millions of developers all around the world and they can contribute to any open source projects. I truly believe open source technology is a qui
Read more

Git : Rebasing Refactoring Amending

-
Image
As if I still don't know everything about git. This week learn about rebasing and amending, rewriting git history as the prof described it. So let's say you're writing a word document and you're in the editing phase. You violently mash Ctrl+S every time you make a small fix. Adding punctuation, deleting a word, making a new line, you save again and again and again. Now imagine if you had a log for every time  you save that file, like a git commit. Now that's a lot of entries, and we as coders do this with git commiting as well, but with git saving and tracking each one of those commits, our logs get a bit convoluted and messy. That's why git rebasing and amending is here to save the day. So for this week's lab our prof wanted us to practice these new git concepts by polishing our code and git commiting to our hearts content, since we will be rebasing in the end. So I made my changes and made a couple of commits to the code. Once I was satisfied with the chan
Read more