Skip to content
Snippets Groups Projects
  1. Jan 18, 2022
  2. Nov 22, 2021
  3. Nov 17, 2021
  4. Nov 15, 2021
  5. Nov 12, 2021
  6. Nov 04, 2021
  7. Oct 08, 2021
  8. Oct 06, 2021
  9. Sep 08, 2021
  10. Aug 10, 2021
  11. Aug 06, 2021
  12. Aug 03, 2021
  13. Jul 09, 2021
  14. Jul 01, 2021
    • Kshitij Sobti's avatar
      refactor: Rename CourseEditLTIFieldsEnabledFlag to... · 6fb86793
      Kshitij Sobti authored
      refactor: Rename CourseEditLTIFieldsEnabledFlag to CourseAllowPIISharingInLTIFlag and use it for LTI1.3
      This commit renames the CourseEditLTIFieldsEnabledFlag to CourseAllowPIISharingInLTIFlag since the aim is to expand its scope to all LTI-related PII sharing. It also removes the current LTI1.3 waffle flag for PII sharing.
      Unverified
      6fb86793
  15. Jun 14, 2021
  16. Jun 09, 2021
  17. Jun 05, 2021
  18. Jun 03, 2021
  19. Apr 28, 2021
  20. Apr 21, 2021
  21. Apr 13, 2021
  22. Apr 09, 2021
  23. Mar 22, 2021
  24. Mar 19, 2021
  25. Mar 18, 2021
  26. Mar 03, 2021
  27. Feb 25, 2021
    • stvn's avatar
      fix: Manually backfill lti_config dicts · 7082a991
      stvn authored
      The difficulty here is that the empty string in an invalid JSON
      dictionary (as opposed to None/NULL or '{}' which is just "blank");
      attempts to instantiate models would fail, given the invalid data. This
      meant we couldn't use the Django ORM to handle the migration entirely;
      we need to craft some raw SQL to work-around these checks and
      limitations.
      
      Related-To: 42a9e342
      Related-To: https://github.com/edx/xblock-lti-consumer/pull/144
      7082a991
  28. Feb 24, 2021
    • stvn's avatar
      fix: Manually backfill config_id UUIDs again · 42a9e342
      stvn authored
      The previous backfills handled NULL entries;
      this handles empty strings.
      
      The difficulty here was that since the empty string in an invalid UUID
      (as opposed to None/NULL which is just "blank"), attempts to instantiate
      models would fail, given the invalid data. This meant we couldn't use
      the Django ORM to handle the migration entirely; we need to craft some
      raw SQL to work-around these checks and limitations.
      42a9e342
  29. Feb 23, 2021
Loading