[
https://issues.apache.org/jira/browse/SHINDIG-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629091#action_12629091
]
Chris Chabot commented on SHINDIG-576:
--------------------------------------
On the list Cassie Doll responded:
"No - these are not the correct changes. The javascript api should not have
changed at all. The jsonrpccontainer.js file converts the gender field from
a string into an enum and should also be fixing up the name fields.
Is the php land still on the restfulcontainer.js file? Maybe you just need
to copy the conversions I did in jsonrpccontainer to the restfulctonainer.
(I actually have a todo to pull it into a separate file because we will
probably need very similar code for opensocial8to9.js (when we write it) -
so pulling it into a separate file would get both containers on the right
track)"
Since we are currently using the restfulcontainer code, it seems our solution
is to copy the conversions from the jsonrpccontainer.js implementation.
> change name.unstructured to name.formatted and add displayName to output of
> RESTful getPeople response in shindig-java
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-576
> URL: https://issues.apache.org/jira/browse/SHINDIG-576
> Project: Shindig
> Issue Type: Bug
> Components: RESTful API (Java)
> Reporter: Joseph Smarr
>
> As per the 0.8.1 alignment with PortableContacts, the name.unstructured field
> should now be name.formatted, and there should be a top level displayName
> field, which is required, and in general will be the same as name.formatted,
> but could be something else if name is missing (e.g. nickname, email,
> company, or whatever is the primary textual description of this contact).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
