ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
32,691 Commits 324 Branches 20,019 Tags 1.7 GiB
Commit Graph

4 Commits

Author SHA1 Message Date
Landon Wilkins 58e4df2494 da licença part 37 
add consistent license headers to all source files
(ruby, coffeescript, javascript)

except for vendor files

Change-Id: Ibc881431ca51b7da3b0d3182033e95ebf7d6e524
Reviewed-on: https://gerrit.instructure.com/110067
Tested-by: Jenkins
Reviewed-by: Jon Jensen <jon@instructure.com>
Product-Review: Jon Jensen <jon@instructure.com>
QA-Review: Jon Jensen <jon@instructure.com>
 2017-04-27 22:44:36 +00:00
Cody Cutrer a9f770be82 streamline change_column_null_with_less_locking 
just add the behavior to the regular method, so that we don't have a
special method for Canvas

Change-Id: Ib1d580d05ace02d6661b86a246816db35d0539d9
Reviewed-on: https://gerrit.instructure.com/106777
Reviewed-by: Neil Gupta <ngupta@instructure.com>
Tested-by: Jenkins
Product-Review: Cody Cutrer <cody@instructure.com>
QA-Review: Cody Cutrer <cody@instructure.com>
 2017-03-29 18:07:16 +00:00
Cody Cutrer 884534ffa5 Rails 5: fix Rails version migration deprecation warning 
also pins all migrations to Rails 4.2 semantics

Change-Id: I386566f7a1f3e3e8aa31675f467c87c443457aee
Reviewed-on: https://gerrit.instructure.com/95571
Reviewed-by: Simon Williams <simon@instructure.com>
Tested-by: Simon Williams <simon@instructure.com>
Product-Review: Cody Cutrer <cody@instructure.com>
QA-Review: Cody Cutrer <cody@instructure.com>
 2016-11-17 23:46:22 +00:00
Cody Cutrer 6ff358abca notification preferences API 
closes CNVS-5797

test plan:
 * GET /api/v1/users/self/communication_channels/:id/notification_preferences
   should return your preferences
 * GET .../notification_preferences/<one of the named notifications returned above>
   should return a single preference
 * PUT .../notification_preferences/<notification>?notification_preferences[frequency]=never
   should update it (will return it, and confirm by getting it again
 * PUT .../notification_preferences?notification_preferences[<notification>][frequency]=never&
   notification_preferences[<another notification>][frequency]=never
   should update two preferences at once
 * other allowed frequencies are immediately, daily, and weekly
 * repeat replacing the communication channel's id by email/<email address>
 * repeat by using an actual user id instead of self. users should
   not be able to view or update each other's preferences. admins
   should only be able to view, not update (the update routes only exist for "self",
   so you'll get a 404 instead of a 401 for them)
 * regression test notification preferences UI

Change-Id: I107f68a44cb68ee1675ad50ff7123e26d7765450
Reviewed-on: https://gerrit.instructure.com/26311
Reviewed-by: Cody Cutrer <cody@instructure.com>
Tested-by: Jenkins <jenkins@instructure.com>
QA-Review: August Thornton <august@instructure.com>
Product-Review: Cody Cutrer <cody@instructure.com>
 2013-12-20 22:44:02 +00:00