glazed-donut VS telescope

For the past week, I have been researching on where to release my command line interface (cli), glazed-donut.

For this week, I set up a CI pipeline for yassgy with GitHub Actions. I also contributed to glazed-donut, by creating a few test cases.

Throughout the last months while I was working as a Software Developer Intern and on my my ssg repo, I was hardly ever touching front end. I missed working on front-end a lot, so as my first PR for the #hacktoberfest challenge, I decided to take on a small issue related to front end.

This week I was doing some refactoring for my glazed-donut repo. Since its creation, the features kept coming in every week, but there was no refactoring done whatsoever, so... it got pretty messy😅

This time, I've added two features for Glazed-Donut. It now supports the --lang (or simply -l) command, where you can specify a language tag (ex: fr-CA for Canadian French) and it will set the lang attribute in the generated HTML files to whatever value you put. By default, it will set the lang attribute to en-CA. It is done so that the browser can know what language the contents of the file are, and how it can better interpret them.

Irene also added a similar feature to my glazed-donut repo. The feature she has added was a Markdown file support that's able to convert all # into

After I built the Glazed Donut, I had a wonderful opportunity to explore a similar project shinny-ssg by doing some testing and reviewing and get my glazed-donut tested as well.

I tested her application glazed-donut with all test cases and her code nailed it. All the features worked as expected and it generated appropriate messages to the users when there were any errors/exception. The only problem I could find about it is in generateHTML method , which she should have replaced the with white space. Other than that, just a few minor typos on the read me file, but nothing major. When she reviewed my code and tested my app, I appreciated that she really spent the time to check every detail, giving me very sound advice and helped me file bugs which I did not find before. First, she mentioned the naming convention in C# and explained in details the good practices in the industry. Second, she found a bug in my Page class which created an extra tag. Third, my exception handling was not good enough and she guided me to make it better. In the end, I am able to fix most of the issues but I need more time to improve the code and make it flawless.

You can view the project here.

It all starts with an old 400 error that was occurring in Telescope for a while now, first documented here.

Sattelite for the back end

There are a few places to start with this, one is that we have an issue in Telescope that relates to what I think is the session no longer existing in certain situations that results in a 400. This will give me an opportunity to take a look at Telescopes auth flow. I still am kind of unfamiliar with Telescope despite having been in the last OSD course. I know that we use passport SAML in Telescope however and in the new project we will use a different library called SAMLIFY.

The project is currently in the planning phase, and being part of the development team, I have been researching ways to add relevant bits of Satellite in the Remix Blues Stack project, we intend on using for Starchart.

As a good well-established project, Telescope provides a great environment setup guide, which covers most use cases.

It's been a year since I was supposed to work on Telescope for a class. When the war in Ukraine started in February 24th, 2022, I almost fully stopped contributing. Now, this year I am trying to do more, even though it's not my class anymore. Because I wish that I did more back then.

This week, I decided to setup Telescope locally. I had previously contributed to telescope and had set it up already. However, I faced some problems starting it up locally after a shutdown and startup sequence. This was hard to debug since there was no error message, just containers on docker would not start up even after waiting for several minutes. These problems would fix after a restart or just randomly after a few tries. So, I decided to go through the setup again.

Task This week, I try to revisit my setup for running the Telescope project, a single page website that aggregates blog posts.

This week, I finished implementing the feature for filtering out irrelevant feed URLs. Previously, I had added a function for the filtering but had to write the test for it.

The two PRs(1 2) mentioned last time were merged without a hitch. For the one that's about parsing Twitch channel feed URL, the maintainer and I agreed that there should be a follow-up issue opened to expand it to YouTube Channel(s). They also found another bug in the sign-up that should exist as its own issue about the RSS feed URL(s) having incorrect domain. For details about them, please see my last post.