badge-generator VS yassgy

I use a workflow similar to the one above that is implemented in my Badge Generator web app, which is built in Vue and Yarn.

Looking through my classmates' contributions for Hacktoberfest, I found badge-generator - a cool tool that helps us create markdown badges for our documentations. The owner wants to implement the dark mode for the site, and since the tool is written with VueJS, I decided to challenge myself as I could also continue to learn this framework.

Eventually, I remembered one of the repos that I've used before to contribute to one of the Hacktoberfest issues, I thought that it would be nice to give back (hint hint😉😉😉 something to think about when looking for an issue... hint😉) to that repo. I quickly gave up everything I was doing and went to check it out to see if it is even active and if it has any open issues I could work on. To my surprise, no one except the author has ever contributed to that before, so I am now officially one of the first contributors there.😋

After browsing for a while, I found MichaelCurrin's project, badge-generator. The project is a simple interface for simplifying the creation of badges, used in several open source projects to show things like the version number of the project, whether the project is currently building, etc. A badge usually looks like this:

I learned was that even if an issue seems small and something that you can handle, it doesn't mean you will not learn a lot out of it. During the process, I learned about a handy open source repo that helps to generate badges to make README files look prettier. And a cool tool that has all the emojis you need for your frontend.

badge-generator

This time, I would like to talk about publishing yassgy to crates.io, and the process I went through, in the case there is a fellow developer who is going to publish their application.

In Rust, there is a similar mechanism, however, there is a slight difference and that is in the fact that it is built-in. All integration tests found in the tests folder can access the application code to test it, if the application code is found in the lib crate. This was the main issue. Before, yassgy had all of the code placed inside the binary crate, making it inaccessible for the tests.

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.

I learned enough Rust to add a feature!!

However, how good is this branching feature? This is what I decided to learn when working on my static site generator, yassgy, by implementing two features on different branches, parallel from each other.

This small assignment was being worked on simultaneously with the 0.1 release of our SSG tool. The assignment, in basic terms, asked us to let somebody review our code and file issues or PRs to the repo, and we should also do the same with that person's project, also hosted on GitHub.

I am proud to announce the release of Yassgy, version 0.1!