1. 12 Jun, 2017 1 commit
  2. 27 Apr, 2017 1 commit
  3. 11 Apr, 2017 1 commit
  4. 30 Mar, 2017 1 commit
  5. 22 Dec, 2016 1 commit
  6. 20 Dec, 2016 1 commit
  7. 30 Nov, 2016 2 commits
  8. 18 Nov, 2016 1 commit
  9. 02 Nov, 2016 1 commit
  10. 25 Oct, 2016 1 commit
  11. 13 Oct, 2016 1 commit
  12. 07 Oct, 2016 1 commit
  13. 06 Oct, 2016 1 commit
  14. 13 Sep, 2016 1 commit
  15. 08 Sep, 2016 1 commit
    • Update correct persistent score · 31953c5e
      * First take at forcing a subsection's grade to update when a signal is
        sent that a problem's score has changed
      * Refactor signal handler connection.
      * Expand bokchoy tests to cover progress page
      * Add some grading unit tests
      
      TNL-5394
      TNL-5364
      Eric Fischer committed
  16. 23 Aug, 2016 1 commit
  17. 03 Aug, 2016 2 commits
  18. 22 Jul, 2016 1 commit
  19. 07 Jun, 2016 1 commit
  20. 03 May, 2016 1 commit
  21. 02 May, 2016 1 commit
  22. 28 Apr, 2016 1 commit
  23. 08 Apr, 2016 1 commit
  24. 07 Apr, 2016 1 commit
  25. 03 Mar, 2016 1 commit
  26. 09 Dec, 2015 1 commit
  27. 22 Nov, 2015 1 commit
  28. 10 Nov, 2015 1 commit
  29. 26 Oct, 2015 1 commit
  30. 21 Oct, 2015 1 commit
  31. 21 Sep, 2015 1 commit
  32. 08 Sep, 2015 1 commit
  33. 04 Sep, 2015 1 commit
  34. 03 Sep, 2015 1 commit
  35. 01 Sep, 2015 3 commits
  36. 27 Aug, 2015 1 commit
    • [LTI Provider] Grade passback for non-leaf blocks. · 9e6c4491
      This change allows graded assignments to be added to a campus LMS
      regardless of the granularity at which the problem sits. Previously
      a grade could only be returned if the usage ID for the problem itself
      was specified in the LTI launch.
      
      The code assumes that courses taking advantage of this functionality
      are arranged in a hiearchy (with sections being parents to verticals,
      and verticals being parents to problems). When a grading event occurs
      it traverses the parent hiearchy to identify any previous graded LTI
      launches for which the new scoring event should generate a grade
      update. It then calculates and sends scores to each of those outcome
      services.
      
      Since grade calculation is an expensive operation, the code optimizes
      the case where a problem has been added only once as a leaf unit. In
      that case it is able to behave as before, just taking the grade from
      the signal without having to calculate grades for the whole course.
      Phil McGachey committed