Do not suggest props that are not compatible with the version of the vcard

[skjnldsv]

On the add new property, we should not allow the addition of properties that are not allowed on the vcard rfc.

There is an issue regarding the allowed data on the ical.js: kewisch/ical.js#363

https://github.com/mozilla-comm/ical.js/blob/d26b19fa5adb4d3d6e03bff6c6e4c0705c12ab11/lib/ical/design.js#L873

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[spoorun]

The issue here one can see is that when a User creates a new contact through the app, it appears to be automatically created as vCard 3 rather than vCard 4, with no option to force vCard 4.
For those Users wishing to sync with vCard 4 services, this is problematic.

[skjnldsv]

@olantrust We're creating vcard4 by default :)

contacts/src/views/Contacts.vue

Lines 310 to 318 in 6a9025c

	async newContact() {
	const rev = new VCardTime()
	const contact = new Contact(`
	BEGIN:VCARD
	VERSION:4.0
	PRODID:-//Nextcloud Contacts v${appVersion}
	END:VCARD
	`.trim().replace(/\t/gm, ''),
	this.defaultAddressbook)

[spoorun]

@olantrust We're creating vcard4 by default :)

contacts/src/views/Contacts.vue

Lines 310 to 318 in 6a9025c
async newContact() {
const rev = new VCardTime()
const contact = new Contact( BEGIN:VCARD VERSION:4.0 PRODID:-//Nextcloud Contacts v${appVersion} END:VCARD .trim().replace(/\t/gm, ''),
this.defaultAddressbook)

OK, just each card that I download from new contacts created in Contacts App v 3.10 are specified as VCARD Version 3.0.

[skjnldsv]

@olantrust this is a server issue I guess then! 🤔
EDIT: #4038