[
https://issues.apache.org/jira/browse/SHINDIG-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626789#action_12626789
]
Chris Chabot commented on SHINDIG-543:
--------------------------------------
Hey Ram, Indeed the shindig/config/container.js (or the <foo>.js that matches
the ?container=<foo> flag of the request, if any, see
src/gadgets/ContainerConfig.php as reference, would be nice if you could just
use that class instead of duplicating code) is the right place to extract the
information, because having 2 places to define the supported fields would only
be much more confusing.
Another thing to keep in mind is preventing hard coding for the root key to
look for, right now it's "opensocial-0.8", but in a couple of months that might
be 0.9 already :) So it's probably best to walk through the keys, match it
against opensocial-<foo>, and use it's supportedFields entry.
Hope that's of some help, if not please let me know! :)
> Get supportedFields through the RESTful API
> -------------------------------------------
>
> Key: SHINDIG-543
> URL: https://issues.apache.org/jira/browse/SHINDIG-543
> Project: Shindig
> Issue Type: New Feature
> Components: RESTful API (PHP)
> Reporter: Chris Chabot
> Priority: Critical
>
> See
> http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/2ce4adb503576439?hl=en
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
