Github user vladimir-kotikov commented on the pull request:
https://github.com/apache/cordova-plugin-contacts/pull/95#issuecomment-161548065
@dblotsky, as @purplecabbage mentioned, there is no way to cover this by
autotests, because from JS perspective everything works well - we convert a
date to timestamp and send it to native, then we get _exactly the same_
timestamp from native (because there was no conversion made on native side).
BTW, this might be a perfect case to cover with UI autotest, @alsorokin
working on.
@riknoll, The issue is in format which the date should be stored in
contacts database. The android docs doesn't specify this format (except from
the fact that [it should be a
'TEXT'](http://developer.android.com/reference/android/provider/ContactsContract.CommonDataKinds.Event.html#START_DATE)),
but the birthday in contact card is _displayed correctly_ only if specified as
`dd-mm-YYYY` (from my experience).
There is no inconsistence in Contact objects structure on JS side - the
`birthday` field is always a valid `Date` object or `null`, despite of current
platform.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
