[
https://issues.apache.org/jira/browse/SHINDIG-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606748#action_12606748
]
Chris Chabot commented on SHINDIG-392:
--------------------------------------
Ok so based on the comment on shindig-dev, there's actually no problem with
this? If so please give me a case in which it doesn't do what it should be
doing :-)
At first glance the code bruno contributed makes sense, if the idSpec is not a
predefined type (owner, viewer, etc), then you can assume it is a list of ID's
([1,3,4]) so the logic "If is not a predefined type, and not empty, then its a
list of id's" sounds fine to me.
> 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.
