Costs to Expect API

The Costs to Expect API is ready for release*.

I’m going to continue development to add additional features and start working on the summary endpoints and endpoints required for the companion website, however, the API itself could be released today.

The API is ready, five years and two months of child costs exist, the two need to be put together.

I’m going to work with my Wife to review and categorise the data. Our data is categorised, however, for the API we want to break the data down a little more, our data is split into thirteen categories, we intend to have fewer base categories and subcategories to provide the detail.

*I’m not setting a release date, it will be soon though, I want to get the API out before I look for a new contract and go back to work.

Once the API is out, I will start development on the companion website for data input (preview for iOS app), the iOS app and the website to display the data.

We have several long-term plans for the Costs to Expect API and website, one being to allow additional data, for example, localised costs for childcare/hobbies etc. Our intention is you will be able to augment our base data to get a more accurate idea.

Open Source is awesome, PHP Quill Renderer v3.01.0

A few hours after arriving at work I got an email from GitHub letting me know about a posted issue on one of my Open Source libraries, turns out I had missed a couple of things in my testing.

When I create a library, I have a use case in mind; typically I’m trying to solve a problem specific to one of my projects, having an extra set of eyes reviewing my libraries and using them differently is terrific.

I’m always happy to receive bug reports; each fix improves the library. Hopefully, there will not be too many more but if there are I will jump on them to fix the issue.

I have released v3.01.0 of my PHP Quill Renderer; Parser::load() wasn’t resetting the deltas array, and the Compound delta was incorrectly trying to handle images with multiple attributes assigned.