Skip to content
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.

Sign up for GitHub

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

Jump to bottom

VCARD components cannot contain more than 1 FN despite Specification #69

Closed
hildigerr opened this issue Mar 3, 2017 · 0 comments
Closed

VCARD components cannot contain more than 1 FN despite Specification #69

hildigerr opened this issue Mar 3, 2017 · 0 comments
Assignees
@wpercy
Milestone
0.9.5

Comments

@hildigerr
Copy link

hildigerr commented Mar 3, 2017 •
edited by wpercy
Loading

According to the vCard Format Specification (RFC 6350), the FN identification property has a carnality of 1* --that is 1 or more. However, if I add more than 1, I cannot add a value for the second FN and attempting to serialize it produces the object.base.ValidateError message which gives name to this issue.
@wpercy wpercy self-assigned this Apr 11, 2017
tasn added a commit to tasn/vobject that referenced this issue May 31, 2017
@tasn
vCard validation: allow having more than 1 FN fields.
df03fc3 
According to the spec, there can be 1 or more FN fields.
Current code limited it to just 1.

Reference: https://tools.ietf.org/html/rfc6350\#section-6.2.2.

Fixes skarim#69
@wpercy wpercy closed this as completed in 1d083fc Jun 20, 2017
@wpercy wpercy modified the milestone: 0.9.5 Jun 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wpercy wpercy

Labels
None yet
Projects
None yet
Milestone
0.9.5
Development

No branches or pull requests
2 participants
@hildigerr @wpercy