@@ -62,9 +62,64 @@ actions and reducer; thus, this module.</p>
62
62
<dd ><p >This module provides a service for conventient access to Topcoder APIs.</p >
63
63
</dd >
64
64
<dt >
65
- <a href =" services/challenges.md " >services/challenges</a ></dt >
66
- <dd ><p >This module provides a service for convenient manipulation with Topcoder
67
- challenges via TC API.</p >
65
+ <a href =" services.billing.md " >services.billing</a ></dt >
66
+ <dd ><p >Access to Topcoder billing accounts.</p >
67
+ </dd >
68
+ <dt >
69
+ <a href =" services.challenges.md " >services.challenges</a ></dt >
70
+ <dd ><p >This module provides a service for convenient manipulation with
71
+ Topcoder challenges via TC API.</p >
72
+ </dd >
73
+ <dt >
74
+ <a href =" services.communities.md " >services.communities</a ></dt >
75
+ <dd ><p >Communities service.</p >
76
+ </dd >
77
+ <dt >
78
+ <a href =" services.direct.md " >services.direct</a ></dt >
79
+ <dd ><p >The Direct service takes care about communication with Direct APIs:
80
+ projects, billing accounts, copilots, all these stuff should be added here,
81
+ at least for now.</p >
82
+ </dd >
83
+ <dt >
84
+ <a href =" services.groups.md " >services.groups</a ></dt >
85
+ <dd ><p >Service for communication with group-related part of Topcoder API.</p >
86
+ <p >NOTE: Through this file, and in related contexts, by loading a user group,
87
+ or user groups data, we refer to loading the information about descendant
88
+ user groups; i.e. given some user group(s) we speak about loading the sub-
89
+ three of related child groups.</p >
90
+ <p >By group maps we refer to the object having group IDs as the keys, and
91
+ group data objects as the values. Any group object included into a group map
92
+ has its " ; subGroups" ; array (if present) replaced by " ; subGroupIds" ; , that lists
93
+ only the IDs of immediate child groups; actual child group objects from
94
+ " ; subGroups" ; are recursively added to the top level of the group map.
95
+ Also each group in the group map is timestamped to keep caching of
96
+ the loaded data.</p >
97
+ </dd >
98
+ <dt >
99
+ <a href =" services.members.md " >services.members</a ></dt >
100
+ <dd ><p >This module provides a service for searching for Topcoder
101
+ members via API V3.</p >
102
+ </dd >
103
+ <dt >
104
+ <a href =" services.reviewOpportunities.md " >services.reviewOpportunities</a ></dt >
105
+ <dd ><p >This module provides a service for retrieving Review Opportunities and
106
+ submitting applications.</p >
107
+ </dd >
108
+ <dt >
109
+ <a href =" services.terms.md " >services.terms</a ></dt >
110
+ <dd ><p >This module provides a service for convenient manipulation with
111
+ Topcoder challenges' ; terms via TC API.</p >
112
+ </dd >
113
+ <dt >
114
+ <a href =" services.user-settings.md " >services.user-settings</a ></dt >
115
+ <dd ><p >User Settings service. Corresponding part of the backend is
116
+ implemented as a separate Heroku App, which is set up only for prod.
117
+ Currently, we use it to save user-defined filters in the challenge search.</p >
118
+ </dd >
119
+ <dt >
120
+ <a href =" services.user.md " >services.user</a ></dt >
121
+ <dd ><p >The User service provides functionality related to Topcoder user
122
+ accounts.</p >
68
123
</dd >
69
124
</dl >
70
125
0 commit comments