Release 0.4 : Migration Progress

-

So for the past week I've been working on and off with migrating the components for telescope I've taken from the list that needs porting. 

The Components I've undertaken are

  • BackToTopButton
  • GitHubContributorCard
  • DynamicImage
I was hoping to work on one of the Search components since I've spent so much time previously working on them, but it looks like some of my other peers have already beat me to it. Nevertheless, I still wanted to help with the migration as much as I can.

So I used this reference our professor had posted in the Meta issue regarding migrating from Gatsby to Next JS.

The first thing to do is to edit the dependencies in the package.json, since it's different than the one used for the Gatsby front-end. We will still need the Material UI modules for our front end, but all the gatsby dependencies will now be removed in place of something else.

For example, the Image component used from gatsby-image will now be replaced with next/image. Where as in build times, the images are optimised using the gatsby-image component, with the next/image component images are optimised on demand when they are requested.




Querying data is also different and I'm currently in the process of trying to migrate components such like StaticQuery and graphql from gatsby to its next counterparts.

As for the other 2 components, they were fairly simple, but usually that's a sign that there's a lot more to be done. What I've done so far is kept the most of the code the same but changed the way functions and objects are coded to its typescript version. So declaring variables is slightly different. Now, I'm waiting for them to be reviewed by the other maintainers of the repo for their input.


So far I feel like I'm making progress but I just know this is going to be harder than it seems.

Thanks for reading

Comments

Post a Comment

Popular posts from this blog

HacktoberFest Entry No.2

-
Image
So around last week I found a great github repo of a chrome extension that previews contents of a webpage when you hover over a link. I stumbled upon it after a suggestion from my professor about taking a look at chrome extensions for a possible repo to contribute to. I'm glad I did because this was a chrome extension that was interesting, seemed practical and had a maintainer who was keen on receiving contributions to better his program. The extension is called Survol First I had to install it and test it out first, can't just contribute to a repo meaninglessly just to force a pr. I tested the extension and liked the functionality, it was useful and is well designed. Makes it all the more exciting for me to try and contribute to it. So I read the docs and learned how the extension worked. It uses a javascript file to inject html elements through the dom and uses mousemove event to detect anchor links to request information of a page, and positions and fills the div with conten...
Read more

Lab 1 : Our First Open Source Contributions

-
So for Lab 1 our tasks were fairly simple. Find a partner to review a repo on and make contributions, no matter the scale, to their code. Be it a suggestion for their code, reporting an issue, or even fixing up small details in their readme. So through slack I partnered up with one of my coursemates  Niaz Much like me, he wrote his code in nodejs, so it was perfect since I can go through his code easier through my understanding of node. His code, though written in the same language, differed from mine a lot. For one, he didn't use yargs so he had to process the arguments manually, and secondly he didn't use fetch and opted for a module called linkinator. No problem, in fact it's an opportunity for me to understand the logic and components that he used. I forked a copy of the repo, cloned it and tested it out for myself. The code worked perfectly as intended and processed urls well. Functionally, I couldn't find find anything in the code I could identify as a flaw or imp...
Read more

Hack.... vemberfest.. PR No. 3

-
Image
OK so this is pretty long overdue (sorry Prof!) And I still have one more pull request to go and that's on me yes. BUT, this week I spent working (or should I say learning) on our course's aggregated blog website which coincidentally, our prof is making us work on this week for the lab, so I guess I got a good head start going on.  So I took on an issue that seemed pretty straight forward in the repo. It was to change the functionality of the search bar when filtered by author. Seemed pretty straightforward enough, so I went ahead, forked the repo and cloned it on my computer. Now the reading begins, the lengthy process of coding. And the fact that this was a whole website coupled with different technologies that I'm not familiar with only made it waaayyy longer, which maybe is a sign that I should have started working on this much much earlier. But that's what happens when your time management skills is hot garbage. Anyways, I spent the next few days learning about eac...
Read more