You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 22, 2018. It is now read-only.
In most of the 'note' records in tables within bhima, we template in the date of the transaction. This is a useful practice, but the dates often end up rendering as a long date string rather than a nicely human readable and parseable date. Here's an example, from the purchase order creation page.
There are several issues with this:
The dates are verbose. A simple 'DD/MM/YYYY' reduces the bandwidth required to send the date and the storage capacity needed in our database dumps.
They are in English, which is meaningless to the majority our clients.
They are difficult to parse, so searching the text for a particular date is more difficult.
I propose we store all our dates as either a) 'DD/MM/YYYY' or 'DD-MM-YYYY' for simplicity's sake. There are already several services that do this well, notably util and DateService. We should change these dates where we find them.
The text was updated successfully, but these errors were encountered:
In most of the 'note' records in tables within bhima, we template in the date of the transaction. This is a useful practice, but the dates often end up rendering as a long date string rather than a nicely human readable and parseable date. Here's an example, from the purchase order creation page.
There are several issues with this:
I propose we store all our dates as either a) 'DD/MM/YYYY' or 'DD-MM-YYYY' for simplicity's sake. There are already several services that do this well, notably
util
andDateService
. We should change these dates where we find them.The text was updated successfully, but these errors were encountered: