Addressbook Contact Model esoterics

Discuss about Group-Office development here

Moderator: Developers

Posts: 66
Joined: Fri Jun 21, 2013 2:55 pm

Addressbook Contact Model esoterics

Postby richarddodd » Fri Jul 04, 2014 10:41 am

Hi Merijn

I was wondering if you would consider 2 things for groupoffice
1) In the addressbook,
i) The 'first_name' and 'email' fields are required for a contact, but in function init() they are not marked required. Would it be ok to make them required, so I can auto-detect this for an import into contacts?
ii) The 'birthday' field doesn't follow the date pattern of other fields (it uses date, others use int(11) (timestamp)). This makes it hard to write a generic importer as I cannot use the model columns to detect the column type. Would you consider either changing it to an int, or migrating groupoffice over to use mysql date/time fields?
2) Would you be willing to add code to the validator to detect enums, and validate them as you would other fields. This would allow enum fields to be imported.

I'd be interested to hear what you think about these things!


Who is online

Users browsing this forum: No registered users and 1 guest