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
This bug could lead to some enhancement of IndicatorLibraryDialog UX.
CreatedAt renders on a later date than UpdatedAt. I understand that the created field is related to the day, the indicator was saved into the browser database, instead, it should be set to a date prior. Could be arbitrarily set to two years ago as shown in IndicatorLibraryIndicator.
I am not a big proponent of having this information (createdAt and updatedAt) in a dialog. A 4th column could be used to store the updated date.
Also, we might have to add a createdAt to the defaultIndicatorList. So new indicators are actually dated properly and don't use the workspace installation date by default.
Also, it is noticed that the date and time are rendered using the En/Us format while the chart is using a 24-hour format.
I documented the issue with screenshots
I provided a clear and concise description of what the bug is (see both sections below)
The text was updated successfully, but these errors were encountered:
This bug could lead to some enhancement of IndicatorLibraryDialog UX.
CreatedAt renders on a later date than UpdatedAt. I understand that the created field is related to the day, the indicator was saved into the browser database, instead, it should be set to a date prior. Could be arbitrarily set to two years ago as shown in IndicatorLibraryIndicator.
I am not a big proponent of having this information (createdAt and updatedAt) in a dialog. A 4th column could be used to store the updated date.
Also, we might have to add a createdAt to the defaultIndicatorList. So new indicators are actually dated properly and don't use the workspace installation date by default.
Also, it is noticed that the date and time are rendered using the En/Us format while the chart is using a 24-hour format.
The text was updated successfully, but these errors were encountered: