1. 12 Jan, 2017 1 commit
  2. 18 Jul, 2016 1 commit
  3. 23 Jun, 2016 2 commits
  4. 22 Jun, 2016 1 commit
  5. 21 Jun, 2016 1 commit
  6. 19 Jun, 2016 1 commit
  7. 17 Jun, 2016 1 commit
  8. 26 May, 2016 1 commit
  9. 24 May, 2016 5 commits
  10. 05 May, 2016 2 commits
  11. 03 May, 2016 1 commit
    • Fixes for course updates date validation. · 78af4100
      If the first date the user selects is invalid it is not set on the
      model. This is because jQuery datepicker's getDate returns the
      current date when an invalid value is put in the field and the
      model's initial value is also the current date. So always update
      the date.
      Usman Khalid committed
  12. 02 May, 2016 5 commits
  13. 29 Apr, 2016 1 commit
  14. 28 Apr, 2016 1 commit
  15. 27 Apr, 2016 2 commits
  16. 22 Apr, 2016 5 commits
  17. 14 Apr, 2016 1 commit
  18. 08 Apr, 2016 1 commit
    • Course Updates date validation · 2735fdc2
      TNL-4115. Previously, course updates (which are intended to be posted with
      dates, for sorting in the LMS) could be authored in studio with a valid
      date, nothing, or a random string as the "date" for the update. As there
      is no validation for this in studio, everything succeeded with no warning.
      
      However, the LMS has problems parsing some of these values, and barfs when
      loaded by learners.
      
      The fix does two big things:
      - gracefully handles invalid dates in LMS. These updates are now treated as
      having a date of today, for sorting purposes.
      - turns on validation in studio. Now, it is not only impossible to enter
      invalid dates in studio, but notifications will draw the course author's
      eye if any invalid updates were previously saved.
      
      Test additions for this commit:
      
      Adds:
      - unit test for LMS parsing
      - Jasmine test to confirm invalid dates cannot be set by the user
          -also adds event to setAndValidate instead of using a global object
      - fix for lettuce test
          -It is no longer valid to enter the string "January 1, 2013" as this test
          had been doing. Keyed-in entries must use MM/DD/YY format.
      Eric Fischer committed
  19. 04 Apr, 2016 1 commit
  20. 25 Mar, 2016 1 commit
    • Fix issues with Underscore in the asset pipeline · 6dd09a89
      FEDX-121
      
      The previous approach for handling NPM assets was
      to symlink them into the static directory. This appeared
      to cause trouble with the asset pipeline where the files
      in question were not installed and then old versions were
      picked up instead.
      
      This change instead copies NPM libraries to a new
      static directory so that the pipeline can consume them
      as with any other file. This new directory is added to
      .gitignore so that the files don't get accidentally
      checked in.
      Andy Armstrong committed
  21. 23 Mar, 2016 1 commit
  22. 24 Feb, 2016 1 commit
  23. 18 Feb, 2016 1 commit
  24. 27 Jan, 2016 1 commit
  25. 31 Dec, 2015 1 commit