Introduction
Hello everyone, my name is Dustin. Today, I'd like to talk about the process of contributing to an open source project on Github, which is 🔭.
Process
In this part, I mainly go through all issues that I've worked on and and a little introduction about what it is. And in part 3, I'll give more details about each issue and how I really feel about it.
First issue:
The issue can be found here. This issue was open for quite a long time and was resolved by one of contributors but as the project grew, people introduced the same issue over and over again, so the issue was open again. The issue was about moving from using const fetch = require('node-fetch') to extract it from @senecacdot/satellite as satellite exposes it.
Second issue:
My second issue can be found here
Image using Telescope one day, and you find an interesting post and you want to share it with your friends but the process of going to the original url and copy the url is quite cumbersome, so I introduced a share button which will help user to copy the origin url directly to the clipboard. Apart from that, This issue also contains another potential feature which is bookmarking posts. In my opinion, this feature is quite cool and important as Telescope is about all PULLING all blogs from different sites and different people and putting it in one place. One who likes a blog posted on dev.to by person a and a blog posted on medium.com by person b has no other way but going to original url's and signing up and saving it. What if we can make it way more easy for Telescope's users by implementing bookmarking in Telescope. I already filed an issue for the idea which can be found here. This may be another cool feature so I leave it for future students
Third issue:
My third issue can be found here
This issue was open a year ago but doesn't seem to catch lots of other students' interest. This issue is about showing post count when users do a search. Without post count, user is just like a sailor without a compass. They just keep going and going but don't know where they're going exactly. The issue required me to not only figure out how to work with data returned back but also some styling.
Thank you for reading.
Top comments (0)