-
Notifications
You must be signed in to change notification settings - Fork 12
Format date properties #125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@Sv7enNowitzki could this one be considered too? Would be great to have it for improved UX, because business users at not to used to the ISO format for dates. |
Hello Marten, I have to reject this PR. |
Hi Nik, I just checked again and the logic is only run in an after READ handler on ChangeView so on DB it is as intended still in ISO format. |
Usually such formatting is applied on the UI, not on the API / the protocol. |
Yes. The problem is that in the metadata the field is marked as a string field and thus taken by FE as is. It could also be solved if CAP would send |
Hello @schiwekM Best, |
Agreed, that sounds reasonable |
Hi colleagues,
currently if a cds.Date property is modified it is shown as '2022-12-01' in the change log. This is not really user friendly and thus this PR adds date formatting so the dates show up as they would in UI5, e.g. '01 Dec 2022'
BR,
Marten