This is the site for some documentation regarding Fix, but mostly the dev diary.
Start of the issue IDs, namely a new place for the generation algorithm
Compared to the title, the description class is really simple
Only a few minor fixes
On Saturday, I finished the title class, at least for now.
Infrastructure matters, and it’s frustrating when it just stops working.
std::expectedis not part of the standard library in C++20, I use Sy Brand’s implementation.
On the way to
Today I started to implement the first actual domain class.
A little clean-up work and the last step for the list/create feature file.
After today, the “create” issue scenario is working, and the CLI app does no longer contain functionality that does not belong there.
Today, I took the first step in the direction of DDD: I created an application service that provides access to the domain logic. Every call to the domain logic ba the CLI app will go through this or a similar service.
After the “list” command, “create” was the next thing missing in the CLI app.
Today’s session was spent with the refactorings that have accumulated over the last two days.
Today was about the first functional scenario: getting a list of 0 issues.
The creation of issues is hard to test without being able to list them, and listing issues can only be done if we can create some. Therefore, in this step, I’ll implement the basics of both features in lockstep.
Before I merge the initial features of the CLI app back to the main branch, I want to improve the tooling a bit.
Finalizing the first two BDD scenarios, Fix now returns a proper exit code.
The first TDD session, and seeing how far we have come in passing the first BDD scenarios. Fix shows usage information, no more “hello world!”
Today, I defined the first milestone for Fix and started work on the CLI application.
Just to check that behave works as intended before I dive into writing the first actual feature files for Fix.
I installed Jekyll to have an easy way to provide the dev diary and some other documentation in GitHub pages. It was not as easy as it could have been, but that’s probably my fault.
Today’s work was mostly preparation for the actual start of the project - or restart, I should say.
subscribe via RSS