robinwilliam.hundt authored 7 years ago and Jan Maximilian Michal committed 7 years ago

 * Defnied more APIendpoints for feedback and subscriptions
 * Added the feedback spec to the docs folder
 * Removed tutor and reviewer model. Closes #43 and #68

* The mechanism proposed should work as follows:
  * Tutors can subscribe to certain submission categries (currently
    this includes exam, student or type specific submissions).
    If the set of submissions to corrent is small (student) all
    submissions of that category are reserved for that tutor.
  * A reviewer should also be able to subscribe other users (delegation)
  * A subscription contains assignments or creates them:
    * Only one assignment per user may be active.
    * No new assignments can be added to a subscription after it was
      created while another assignment is present for that subscription.
    * An assignment delegates a submission to a tutor.
    * An active assignment indicates that the tutor is working on that
      assignment
    * After an assignment was finished it is deleted (or archived).
* Upgraded to Django 2.0
* Closes #66, #53.

* The mechanism remains partially incomplete as the progress in
  !67-create-new-model-feedbackline-and-integrate-it is blocking
  progress. Several tests for the API endpoint need to be written
  including. More validation and constraints might have to be added.

Restructured front end code into components and pages
Components should be as dumb and generic as possible. Pages should dispatch actions, pass props to components etc,
Student page now gets submission and submissiontyp from api and displays those to the student
Added information which submissions have been viewed

All the methods in core.tests.data_factories have been deleted and the tests using those are now using the improved make_test_data method from util.factories.
Curiously the tests are running considerably faster on my machine now

I've created a convenience method inside core.tests.data_factories that that can be used to construct a complete grady instance by passing a big dictionary to the method. At the moment one call to the method with some sample data is hardcoded but with some more refinement it might be possible to generate big instances with multiple user/submissions/feedback programatically. This will be especially helpful tu test the layout and structure of the app under more 'real-life' circumstances.