1. 21 Apr, 2016 2 commits
  2. 20 Apr, 2016 4 commits
  3. 19 Apr, 2016 2 commits
  4. 18 Apr, 2016 2 commits
  5. 16 Apr, 2016 1 commit
  6. 15 Apr, 2016 6 commits
  7. 14 Apr, 2016 8 commits
  8. 13 Apr, 2016 2 commits
  9. 12 Apr, 2016 3 commits
  10. 11 Apr, 2016 5 commits
  11. 10 Apr, 2016 1 commit
  12. 08 Apr, 2016 4 commits
    • Revert "Introduce Pattern Library test pages" · 4671970f
      This reverts commit 845e3708.
      Brian Jacobel committed
    • Revert "Introduce Pattern Library test pages" · 36917398
      This reverts commit 845e3708.
      Brian Jacobel committed
    • 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