[pirate-politics] r586 committed - Edited wiki page pp_get_issue_list through web user interface.

1 view
Skip to first unread message

pirate-...@googlecode.com

unread,
Feb 9, 2011, 7:22:50 AM2/9/11
to pirate-poli...@googlegroups.com
Revision: 586
Author: fragro
Date: Wed Feb 9 04:20:19 2011
Log: Edited wiki page pp_get_issue_list through web user interface.
http://code.google.com/p/pirate-politics/source/detail?r=586

Modified:
/wiki/pp_get_issue_list.wiki

=======================================
--- /wiki/pp_get_issue_list.wiki Wed Feb 9 04:18:37 2011
+++ /wiki/pp_get_issue_list.wiki Wed Feb 9 04:20:19 2011
@@ -7,7 +7,19 @@
This tag populates the pp_issue namespace object with an object called
issue_list. Issue list is an array of Consensus objects, not actually
issues. This is to solve a big scalability problem. However each Consensus
object is easily accessible through their reference to their parent object
`content_object`. Within each element of this array, the fields _name_,
_text_, and _topic_ are populated with data. This tag allows for easily
printing a list of all the issues with their information.

==_Arguments and Parameters_==
-This tag takes no arguments or parameters.
+
+#. *dimension*:
+ * This parameter gives a ranking type.
+ * for example: `dimension="hot"`
+ * *All possible parameters:*
+ # `"hot"`: get solutions ranked by current popularity
+ # `"cont"`: get solutions ranked by controversy
+ # `"top"`: get all-time highly ranked solutions
+ # `"new"`: get new solutions
+ #. *topic*:
+ * This parameter is the Topic being requested `{{request.object}}`
+ #. *start*: Start integer index of the for slicing the solutions list
+ #. *end*: End integer index of the for slicing the solutions list

==_Return value_==
This adds the array "issue_list" to the pp_issue namespace object.

Reply all
Reply to author
Forward
0 new messages