Hazel VS go-go-web

I used a workflow template for MSBuild-based projects. When doing this lab exercise I referred to this video by TheCherno, who used the same template for his Hazel Game Engine developed using Visual Studio. The Microsoft Build Engine, MSBuild, is what Visual Studio uses to load and build managed projects. Since I'm also developing my project using Visual Studio, this template seemed like the best option.

Don't write a full blown abstraction, you won't use it. Also Hazel is a great game engine which relies on Vulkan that you could use as well.

And sometimes I feel like 50% of those are copy-pasted from Hazel, which is also far from being commercially viable, despite its popularity.

They're coming from the precompiled header in that project: https://github.com/TheCherno/Hazel/blob/dcdbfe13ac1d06a1650f66719cb4f79ecf310c85/Hazel/src/hzpch.h

https://github.com/TheCherno/Hazel there's a youtube series following the development of this engine, and other useful series on the same channel

Also, I just created premake configurations for the Vulkan SDK. Actually, this is only for the shader compiler and spirv-cross, so there might be more stuff from the SDK to be added.

IIRC, all those engines provide an ECS that could be compared to entt.

Also, there is Hazel[0] which is based on entt and is the subject of an amazing youtube series[1].

IMHO, tinier means less features, at that point what could be considered comparable?

  [0] - https://github.com/TheCherno/Hazel

[metadata] name = gogoweb version = 1.0.3 author = Katie Liu author_email = [email protected] description = Command-line tool that converts .txt or .md files into .html files. long_description = file: README.md long_description_content_type = text/markdown url = https://github.com/kliu57/go-go-web project_urls = Bug Tracker = https://github.com/kliu57/go-go-web/issues classifiers = Programming Language :: Python :: 3 License :: OSI Approved :: MIT License Operating System :: OS Independent [options] package_dir = = src packages = find: python_requires = >=3.7 [options.packages.find] where = src

For this lab exercise I had the opportunity to add unit tests to a classmate's project and experience their CI workflow. For this exercise I worked on go-go-web by kliu57. Go-Go Web is written in Python and uses the pytest testing framework. This was my first time writing tests for pytest, but I found the pytest docs helpful. However, more helpful was the information provided in the associated issue and the tests already written, which helped me write the test I needed in the author's preferences.

This week, I am using Continuous Integration to automatically lint and test my open source project whenever the code is pulled or pushed to GitHub!

This week I want to add a new feature to my text to HTML converter, go-go-web. The feature I plan to add is Markdown Front Matter support. When a user converts an .md file to .html using my program, my program would be able to convert Front Matter in the .md file into metadata tag content in the resulting .html file.

I chose to write my program in Python while she used Java. Aside from syntax differences, she has much more exception handling in her code compared to mine. It made me think that I should add more exception handling to my own code. Having another person test my code definitely helps to find more issues. She discovered that I missed implementing the spec for deleting the default output folder at the start of the run. Also, she uses a VS Code extension called Pylint which helped to find many problems with my code. Pylint found many issues with my code which were not best practice, such as not specifying an encoding when reading from a file, or using an f-string that does not have any interpolated variables.