[
https://issues.apache.org/jira/browse/SHINDIG-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606768#action_12606768
]
Karsten Beyer commented on SHINDIG-392:
---------------------------------------
hmm. Now i understand the intention behind it, but anyway, take this request
from the compliancetest:
[{"type":"FETCH_PEOPLE","idSpec":true,"profileDetail":["id","name","thumbnailUrl"],"sortOrder":"topFriends","filter":"all","first":0,"max":20}]
Obviously this is simply a wrong wrong idSpec, the Exception should be
triggered.
Maybe it would be a good idea to use a regexp to see if it is indeed a valid
idSpec. (i would write it, but was not able to find the specification about how
the idSpec is supposed to look when requesting multiple USER_IDS....)
Another, related problem is that
"idSpec":"USER_IDS"
is handled as a valid idSpec which in my opinion it is not... so it should be
removed from the $types array...
> bug in idSpec.php that doesnt allow array() of user ids
> -------------------------------------------------------
>
> Key: SHINDIG-392
> URL: https://issues.apache.org/jira/browse/SHINDIG-392
> Project: Shindig
> Issue Type: Bug
> Components: Common Components (PHP)
> Reporter: bruno rovagnati
> Assignee: Chris Chabot
> Attachments: idSpec_USER_ID.patch
>
>
> if an array of id (or a single id) is sent for a IdSpec, php will rejected as
> invalid
> ps: this applies to JSON wired stuff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
