1. 29 Apr, 2013 6 commits
  2. 22 Apr, 2013 1 commit
  3. 18 Apr, 2013 3 commits
  4. 17 Apr, 2013 4 commits
  5. 12 Apr, 2013 7 commits
  6. 03 Apr, 2013 3 commits
  7. 01 Apr, 2013 2 commits
  8. 30 Mar, 2013 1 commit
    • Accept either a list of possible values, or a string as a value for · dfd3a699
      comparison of correctness in multiple choice.
      
      Multiple choice code is scattered and sometimes sends a list of
      choices for the value, and sometimes a single string. We used to use
      "in" which scarily handled both cases (list or substring search),
      but that caused a bug when you had two choices like choice_1 and
      choice10. Moving to == caused us to break when lists were sent to
      us. So this ugly code is extra paranoid and checks both possibilities.
      
      This really needs a better cleanup.
      David Ormsbee committed
  9. 29 Mar, 2013 3 commits
  10. 27 Mar, 2013 7 commits
  11. 26 Mar, 2013 3 commits