Month: February 2020

We have fixed two small bugs on the Costs to Expect API.

Fixed

• Select the correct year when validating the min and max year for year validation.
• The logo on the welcome page will redirect you to the API, not the app dashboard.

We have fixed two small bugs on the Costs to Expect Website.

Fixed

• Search the name field rather than the description field.
• Selecting a subcategory will now jump you to the expenses table.

In the newest release of the Costs to Expect API, we add a new `item` type, “Simple items”. The intention is the new `item` type will be used to manage lists and collections.

We found the process of adding a new `type` to be more complicated than it should; we have refactored the item code to organise the different item classes more sensibly.

The full changelog is below:

Added

• We have added a new item type, `simple item`. We intend that the ‘simple item’ type is useful for managing collections. The API will now allow you to list, add, edit and delete them.
• We have updated the summary routes to calculate the correct summaries for the `simple item` type.

Changed

• We have removed the effective date from simple expenses. Our intention is simple expenses are bucket based, not time-based.
• We have updated the copyright for the API. 
• We have moved additional methods in the base `item` classes to reduce configuration code duplication.
• We have simplified the validation classes for `item` create and update requests.
• We have renamed some of the methods on the `item` class to make the intent of the method names more clear.
• We have renamed the item interface class.
• We have moved the `resource type item` classes; they are below the`item` class; there is no need for them to be so low in the structure.
• We have moved the factory class for `resource type` items.
• We have moved the validation classes.
• We have moved the `item` model classes; we have grouped all classes of the same type.

We have released a minor update to the Costs to Expect App. We are adding new `item types` to the Costs to Expect API and needed to push out a small release to ensure the App correctly handles data it doesn’t understand.

The full changelog is below:

Changed

• We have added a helper method to the `Request\Response\Result` class, `hasResponse()`.
• We have updated the `Request\Api` class to ensure a response exists before attempting to cache the result or results from multiple requests.
• We have made some minor tweaks so that the app doesn’t error when an unknown item type gets added to the Costs to Expect API.

We have released a new version of the Costs to Expect Website.

The Website was far too needy and we needed to tweak the cache settings, we are closer to a sensible cache setup and will work to improve it in the future.

The full changelog is below:

Added

• We have added caching for the requests not covered in the v1.11.0 update.

Changed

• We have updated the back-end dependencies.
• We have updated the front-end dependencies and switch to using the slim and minified versions.
• We have refactored the ‘Request/Api’ class to remove code duplication.
• We have increased the cache lifetime to four hours.

Fixed

• We have fixed a typo in the ‘Request/Api’ class.