Fixed #11709 Dates in custom fields not always stored in the correct format #11726
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
Purchase Date
field and every custom field that is of typedate
in the asset edit/create form admits other date formats than our recommended 'yyyy-mm-dd`. As I think the datepicker should be enough to mitigate this issue, I only add a readonly tag to the HTML input, so no manually date is admitted and we always rely on the date picker element to input dates into the system UI.Of course that I open to discuss other possible fixes.
Fixes #11709
Type of change
How Has This Been Tested?
Test Configuration:
Checklist: