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
Existing dateFormat input is nice because I can transform and display my model's dates (that are in ISO 8601) as dd.mm.yy which is more user friendly.
The problem is when I use p-calendar to edit the model. It breaks my model because calendar component sets my dates as dd.mm.yy which is not compatible with angular2's DatePipe, my API, etc ...
Maybe an additional input like internalFormat will help. This may be the format that binds with ngModel.
jQuery UI Datepicker has this feature: dateFormat for parsing and diplaying and an optional altFormat that overrides format shown to the user.
The text was updated successfully, but these errors were encountered:
So you want to use dd.mm.yy for dateFormat when displaying and need an alternative format? Does 1230 and 1231 help your case as well? Can you give us a detailed example with dateFormat, internalFormat and so on.
Yes. The idea was Calendar component to be able to work with 2 formats (display format and binded model format). #1230 & #1231 seem to fix this. I'll try it when rc4 gets released.
Existing
dateFormat
input is nice because I can transform and display my model's dates (that are in ISO 8601) as dd.mm.yy which is more user friendly.The problem is when I use p-calendar to edit the model. It breaks my model because calendar component sets my dates as dd.mm.yy which is not compatible with angular2's DatePipe, my API, etc ...
Maybe an additional input like
internalFormat
will help. This may be the format that binds with ngModel.jQuery UI Datepicker has this feature: dateFormat for parsing and diplaying and an optional altFormat that overrides format shown to the user.
The text was updated successfully, but these errors were encountered: