Yes, it's definitely a schema change and like I said it's a divergence from
the other listings operations -- I'm all for going this route but we should
change over all of the filter/mget queries to this approach if we're in
agreement that it makes sense.


On Mon, Jun 2, 2014 at 1:01 PM, chrisndodge <notifications@github.com>
wrote:

> In lms/djangoapps/api_manager/users/views.py:
>
> >      * Password formatting policies can be enabled through the "ENFORCE_PASSWORD_POLICY" feature flag
> >      * The first_name and last_name fields are additionally concatenated and stored in the 'name' field of UserProfile
> >      * Values for level_of_education can be found in the LEVEL_OF_EDUCATION_CHOICES enum, located in common/student/models.py
> >      """
> >
> > +    def get(self, request):
> > +        """
> > +        Possible use cases
> > +        GET /api/users
> > +        GET /api/users?page=2
>
> I think the meta information is good so either it gets put in the HTTP
> response headers (which is a bit more complicated) or it's in the payload
> body, like it is here. However, my guess is that this is a schema change
> and @martynjames <https://github.com/martynjames> will have to change the
> API client-side code.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/edx-solutions/edx-platform/pull/63/files#r13295133>.
>



-- 
Matthew Drayer
Solutions Architect
edX | MIT
mattdrayer@edx.org