Costs to Expect

For this release, we made the necessary changes to work with v2.11.0 of the Costs to Expect API. As always, while we were making the changes, we tweaked and fixed a couple of things.

Changed

• We are updating the Website to run on PHP7.4.
• We have updated the Website to work with v2.11.0 of the Costs to Expect API. The format of the categories object was updated.
• We have tweaked the Docker setup, we have added a network.

Fixed

• When we hastily added the caching, we did not cache the response headers, only the body. We have updated the Website to cache the response body and headers.
• We have removed a link that would direct the user to a page we know will not have content.

For this release, we made the necessary changes to work with v2.11.0 of the Costs to Expect API. As always, while we were making the changes, we tweaked and fixed a couple of things.

Changed

• We have updated the resource names on our dashboards; the names are now clickable links.
• We have versioned our stylesheet and javascript includes.
• We have updated the App to work with v2.11.0 of the Costs to Expect API; the routes for item category and subcategory relationships have changed.

Fixed

• We have corrected the resource name shown on the resources page.

In this release, we have added additional search and filtering options. The documentation for the API is available at https://postman.costs-to-expect.com; while writing the documentation for the API, we found several small bugs which we have fixed.

Added

• We have added search to the categories summary endpoint.
• We have added search to the subcategories summary endpoint.
• We have added search to the resources summary endpoint.
• We have added search to the resource-types summary endpoint.
• We have updated the transfers collection; you can filter the results by an `item` ID.
• We have updated the partial transfers collection; you can filter the results by an `item` ID.
• We have added additional filtering options for collections. We have added `total` and `actualised_total` range filtering for the `allocated-expense` item type and `total` range filtering for the `simple-expense` item type.

Changed

• We have added the documentation URI to the README and API; the documentation for the API is work in progress; it is almost complete.
• We have added a version query parameter to the CSS include.
• We have removed a unique index on the `item_transfer` table; the index was limiting the ability to transfer an item multiple times.
• We have altered the format of the category and subcategory object for item relationships; the returned object is now a closer match to a category object.
• We have updated the URIs for item category and subcategory assignments; the URI was singular for a collection.
• We have updated the item delete endpoint; we did not return a conflict error before removing relationships.
• We have tweaked the `type` for expense fields; we highlight that the supplied value should be a decimal string.

Fixed

• The `name` field now displays as a required field in the items collection OPTIONS request.
• The `filterable` array shows in the OPTIONS response for resource type items.
• We have updated the namespace in a model.
• We have corrected the case of a model name.
• We have added the migrations for the original item-types, missing from the import.
• We have added a database migration to update the `friendly_name` and `examples` data for `item-types`.
• We have updated the delete item request; we delete the transfer log entries for the item.
• We have updated two `item-type` summary endpoints to show they are sortable by `name`.

Removed

• We have removed the category and subcategory item assigned URIs and replaced them with correctly named URIs for collections.

In this release, we have updated the development dashboards; our dashboards are much closer to what we intend for the initial release. We have also added support for partial transfers and transfers.

Added

• We have added the ability to transfer an item/expense from one resource to another.
• We have added the ability to enter partial transfers for expenses.
• We have added new and improved dashboards to all levels of the site; we show much more information than before, no longer just the total count/cost.

Changed

• We have updated our roadmap; we have decided to expand the initial offering.
• We have added a banner to the top of the site when it is in development mode; we will need to start locking partially developed features due to their scope—being able to see the site mode will hopefully help to reduce errors.
• We have simplified the menu; we don’t need duplicated options in the App menu when there are on-screen controls.
• We have tweaked the mobile layout; add, edit and delete controls are more visible and consistently positioned.

In this release, we fixed several small bugs and made some tweaks. The next release will focus on the dashboards, so we wanted to clear the decks.

Changed

• We have updated the pagination parameters helper; we have added the ability to override the default pagination limit and offset.
• We have updated our cache management class; we can now optionally clear the cache for summary routes.
• We have updated the confirmation messages for items; the confirmation messages will correctly refer to the item type.
• We have updated all the API class fetch functions; we have added an optional parameter to force the local cache to be clear before a fetch.
• We have reviewed the cache keys we clear after API POST, PATCH and DELETE requests.
• We have tweaked the summary blocks again; we are slowly getting the design right.
• We have moved the delete confirmation buttons; the buttons will be above the fold.

Fixed

• We have fixed the pagination on the item detail pages; the pagination controls were non-functional.
• We have fixed an issue with the create allocated expense form; the copy item logic was throwing an error.
• We have fixed an issue with the copy functionality; two values do not get populated on the form.
• We have fixed an issue with the create forms; we are passing an incorrectly formatted date to the date fields.
• We have updated the summaries when a resource has no items/expenses; the last updated date incorrectly gets set to 1st Jan 1970.
• We have corrected a couple of views within the App. We were assuming types of data would exist when they won’t for new users.

In this release, we add the final missing piece for the base of the App, categories management.

Added

• We have added an overview page for resource type categories; the overview page acts as the base for all category and subcategory management.
• We have added the ability to create categories and subcategories. When creating a subcategory, you are not required to assign it to the category you selected initially.
• We have added the ability to delete categories and subcategories. If you are unable to remove a category, we add a message detailing the number of dependant subcategories and linked items/expenses. We provide similar information for subcategories.
• We have added the ability to edit categories and subcategories. 

Changed

• We have tweaked our request and cache classes; in some instances, we were making a redundant call to the cache table.
• We have upgraded our App to the latest version of Laravel v7.
• We have upgraded our server environment to PHP 7.4.

Fixed

• The description for some required textarea fields referred to them as being optional.

In this release, we fix a few small issues and tweak a few things. While we were tweaking, we updated the API to Laravel 7.

Changed

• We have updated all item endpoints to return `updated`; this is the date and time an item was updated, not its category assignments.
• We have updated item collection and show endpoints; we are going to allow the possibility of items not having categories and subcategories. When you add the `include-categories` and `include-subcategories` parameters to a request, we will not exclude items without category assignments.
• We have updated the API to the latest release of Laravel 7.
• We have updated the front end dependencies for the welcome page.
• We have updated the `item-types` route to show additional information on each tracking method.
• We have updated all decimal fields to 13,2 rather than 10,2.
• We have updated all description fields; we have switched all the description fields from varchar(255) to text.

Fixed

• We have corrected a bad link on the landing page.
• We have corrected a typo on the landing page.
• We have switched the table we look at to return created at for an item; we should be using the sub table, not the base item table.
• We have corrected the `/resource-types/` OPTIONS request; `public` is not a required field.

In this release, we have added resource type management, on creating a resource type you select your tracking method. We have also reviewed the App and added help text where we feel the user may need a little guidance.

Added

• We have added the ability to create a resource type; when you create a resource type, you choose your tracking or forecasting method.
• We have added the ability to edit a resource type; the forecasting method does not appear on the edit form; we can’t alter the tracking method once you have created a resource type.
• We have added the ability to delete resource types.
• We have added a new section which will display when there are no resources; the content will help guide the user.

Changed

• We have made some minor tweaks to the styling of tables and definition lists.
• We have reworked the “Start tracking” section; we have added additional information for each of the supported tracking and forecasting methods.
• We have refactored our POST code; a little duplication crept in during the last two weeks.
• We have refactored our PATCH code; a little duplication crept in during the last two weeks.
• We have reviewed our App and added help text to guide and explain.

Fixed

• We have corrected an issue related to editing expenses; our App was throwing a 500 error when editing simple-items.
• We have updated a couple of our create and edit forms; the `required` style was missing from some textarea inputs.

Added

• We have added the ability to delete a resource; a resource is only deletable when it has no expenses or items.

Changed

• We have tweaked our API requests; we will no longer include parameters that we know the API ignores.
• We have updated the App to play better with the Costs to Expect API. Under certain conditions, there is a chance that the subcategory and category values will not save. The App will gracefully handle the malformed data and allow the user to correct the data.
• We have reviewed the item (allocated-expense, simple-expense, simple-item) management code; we have renamed methods to be more explicit about intent and removed the little duplication that existed.
• We have updated our roadmap.

Fixed

• We have fixed the redirect after editing a resource; the App tries to send you to an action that doesn’t exist.
• We have fixed a logic error when calculating whether new data is different to live data for editing; we need to clear the cache before we fetch the live data.
• We have fixed a minor bug with the view helper for our messages, under certain conditions, messages will not correctly display.

In this release, we have completed base item management and started work on resource management. For the next feature release, we are hoping to finish resource and resource type management and start work on the new dashboards.

Added

• We have added the ability to delete an allocated-expense, simple-expense and simple-item.
• We have added the ability to copy an allocated-expense, simple-expense and simple-item.
• We have added the ability to create a resource.
• We have added the ability to edit a resource.

Changed

• We have re-organised our view components ready for the future Laravel 7 upgrade; we want to separate our view components from Laravel.
• We clear the resource collection and item cache upon deletion.
• We have made a few minor tweaks to the data tables at mobile screen sizes; the controls will now hopefully display as intended.
• We have upgraded our roadmap, specifically feature readiness.

Fixed

• We have corrected a spelling error on the landing page.
• We noticed that the categories menu item is missing from the menu under certain conditions; we have added the menu item when it is relevant.