LennahSSG VS GAS-ssg

This week we got the chance to learn how to package and release our SSGs. For my release I decided to use conan as my package manager and GitLab as my package repository. In order to make my package I had to do a few steps first, I needed to install conan and cmake so I could run the commands. I already had cmake installed from testing Andrew's SSG so that was nice. Then I had to make a new GitLab account and link it to my GitHub account so I could import my repo over to GitLab.

Homepage prototype

After I tested everything I was able to do an interactive rebase in Git to merge all my commits together. This was a really neat feature that allowed me to keep my actions/changes organized and it was super easy to do! If you want to take a look at my rebased commit you can find it here. While it looks like a lot was changed it was a lot more manageable because in reality it was a bunch of separate changes. This feature is great to make the commit history look a lot cleaner because I know I am someone who always tends to miss a few things here and there so the tiny commits tend to pile up. Now I don't have to feel as bad when I notice a small thing that needs changing, I can just rebase the commits!

This week, I focused on adding a new feature to my friends site generator, LENNAH SSG. Using a fork of his project with an issue branch, I was able to add support for config files using --config. I also created a draft pull request in order to better communicate our ideas to each other.

Last week when merging my partner's repo we encountered an issue where several files were in conflict. We opted to delete the conflicting files on his end to allow the merge, rather than going through line by line and seeing what was different and he kept backups so as to reintroduce any code that was cut if he so chose.

I decided the two features I wanted to add were things related to the markdown functionality of my SSG. I added support for inline code using the ` syntax and I also added support for the horizontal rule "---" syntax. Thanks to my classmate Gus, it was really easy to augment the existing code to add new features to the markdown support. All I had to do was add some if statements in the markdown handler section of the file reader to check for ` and --- then I just needed to add a new function for inline code generation. You can find the changes for the inline code implementation here and the horizontal rule implementation here.

When Gus made a pull request for my SSG, I found a few things I wanted him to change. First I wanted him to do the same thing as I did for his SSG; make the txt title/header functionality only work for txt files. Second, I noticed that he had if statements like this:

This week I worked on Joshua Li's SSG, LennahSSG again. I added support for markdown files, with the ability to distinguish and generate appropriate HTML tags for bold and italics.

The hardest part of testing/reviewing Joshua's code was finding anything to critique, it was that good. Like when a prof gives you code to work on, logically organized, concise and without mistakes. His code wouldn't compile using g++ originally, but after ignoring the warnings that came up it compiled fine. I think it was just a case of the compiler being finicky, it wasn't liking the multiple declarations of having prototypes earlier in the file but it ran fine after I ignored those. He also included an executable so it wouldn't have made much of a difference regardless.

It was also very nice to have someone else take a look at your code, I made a few silly mistakes that I would probably never have caught because it made sense in my head, such as my versioning being wrong. (Issue).

For this week's lab I packaged my GAS-ssg using conan and CMake.

For this week's lab I implemented Github Actions for my GAS SSG. First I went back and got my tests from last week working. Even though I implemented testing many of them were failing for reasons I didn't have time to get to, which I thankfully got the chance to get figured out this week. The biggest issue that held me up last week was file input not working if I didn't compile my program as I normally do, which I realized was because I hadn't changed my Visual Studio working directory - so my files were being compiled from one folder while the project was in another - obviously the path was wrong when compiling from the project folder.

I picked Gus's SSG to work on. I had work on his project before because we use the same C++ language. We use same testing framework, which is Catch2. So I generally understand how his SSG and Testing Tool work.

For my part I added some testing capabilities to my SSG using Catch2. Catch2 was super easy to set up and involved downloading one header file from their github repo and including it in my program. There are a number of ways you can choose to have Catch interact with your project, either by having Catch define your main i.e

This week I've been implementing some formatting and linting tools for my SSG via clang-format and clang-tidy. It took some doing to get them set up, at first I was very confused about what exactly clang was vs LLVM, what power tools was vs the command line version, and how to use all of the above.

For this week's lab I added a feature from docusaurus to add tags to my GAS SSG's generated HTML pages for added SEO. I started by logging an issue with a description of the functionality I was looking to add, and started working on it.

In the meantime, Kien had (made a pull request of his own)[https://github.com/gusmccallum/GAS-ssg/pull/20] which, less excitingly, had nothing wrong with it. I had to get git cli to add his as a remote branch, and getting that working took some doing but with his help I got it running and was ready to merge. What ensued was a whole lot of banging my head against a wall figuring out why the merge wouldn't work, but eventually triumph and a successful merge. Somehow I had changed the URL to my origin to his branch's URL, but setting that back to the correct one solved my problems and the merge was complete.

======== Gus's Repo: Github Repo My Repo: Github Repo My Issue: Issue #19 My Pull Request: PR #20

This week was a good way to see what the process of doing proper line by line comparison looks like, with two branches being merged one after the other. First, I logged issues for more relevant return codes and markdown horizontal rule syntax.

I worked with Gus again and his GAS-SSG for this lab. I decided for the markdown support, the syntax I would add would be the "# " header syntax. So I added an Issue for adding the markdown support and created a pull request with the forked branch I made. In the code I modified Gus' if statements that handled the file types to include a block that would look for the ".md" extension and also added a new file type code to represent markdown files. Furthermore, I made some adjustments to the file reader so that when it read a txt file it would handle the header/title features that were implemented by Gus. As for handling the markdown syntax, I added a makeHeader1() function that would take a string and add