Brian Palmer 032a317cf1 use defined discussion formats in assignment and submission apis ... fixes #6560 The assignment and submission apis were written before the discussion api, and the response formats diverged. This merges the two formats so that all apis return the same data structures. Also, removed the attachments relation from DiscussionEntry, it's cruft. We have to continue returning the attachments array in the json for now, for backwards compatibility, since it includes the .attachment field as well. test plan: API calls to read discussion assignments and their submissions should now include the full json response data, see the api documentation for the discussions api. Change-Id: Ib394d7e5c3fcf261adb8663470c6822fe2476b03 Reviewed-on: https://gerrit.instructure.com/7395 Tested-by: Hudson <hudson@instructure.com> Reviewed-by: Bracken Mosbacker <bracken@instructure.com>		2011-12-12 09:03:09 -07:00
..
coffeescripts	pull user information from server in conversation user_id links	2011-12-08 12:47:13 -07:00
controllers	use defined discussion formats in assignment and submission apis	2011-12-12 09:03:09 -07:00
helpers	pull user information from server in conversation user_id links	2011-12-08 12:47:13 -07:00
messages	add missing description for ungraded timespan alerts, refs #4317	2011-12-09 12:53:12 -07:00
middleware	sis import api	2011-04-08 15:45:57 -06:00
models	use defined discussion formats in assignment and submission apis	2011-12-12 09:03:09 -07:00
observers	avatar image caching and invalidation, closes #5210	2011-11-16 10:29:42 -07:00
stylesheets	fix spelling of vertical-gradient mixin.	2011-12-08 15:45:53 -07:00
views	don't show the submission score in the coming up tooltip when muted	2011-12-10 16:26:53 -07:00