Dropping ascending order_direction from Discussions API

[Robert Raposa]

Hello Open edXers.

The unpublished Discussion API Version 1, currently used by our mobile applications only, will be dropping support for ascending order_direction from the GET Thread List API.  

There are no known uses of this value, and it is not correctly implemented, so the plan is to simply drop it without a major version upgrade.  This change will be made in the edx-platform codebase on the master branch and will not affect any Eucalyptus release, even future ones.  Ficus will be the first Open edX release with no support for ascending order.

Specifically, the following endpoint with asc parameter will now return a 400 error:

• /api/discussion/v1/threads/?course_id=mycourse&order_direction=asc

Additionally, the Ruby based cs_comment_service will be dropping support for the sort_order parameter altogether.

If you are impacted by this or need any help, please let me know.

Thank you.

--

Robert Raposa

edX | Software Architect  | rra...@edx.org  

141 Portland Street, 9th floor

Cambridge, MA 02139

http://www.edx.org