BigW Consortium Gitlab

  1. 08 Dec, 2017 1 commit
  2. 09 Aug, 2017 1 commit
  3. 08 Aug, 2017 1 commit
  4. 27 Jul, 2017 2 commits
  5. 24 Jul, 2017 1 commit
  6. 14 Jun, 2017 1 commit
  7. 05 May, 2017 3 commits
  8. 22 Mar, 2017 1 commit
  9. 21 Mar, 2017 1 commit
  10. 20 Mar, 2017 1 commit
    • Handle Route#name being nil after an update · 9bf9e6eb
      Robert Speicher authored
      It was possible for the `routes.name` field to be `NULL`, causing
      `name_was` to be `nil` after a rename, resulting a bad first argument to
      `sub` when attempting to rename descendants. This change adds a
      condition to make sure `name_was` is present before attempting the
      descendant update.
  11. 08 Feb, 2017 2 commits
  12. 13 Jan, 2017 1 commit
  13. 19 Dec, 2016 1 commit
  14. 08 Dec, 2016 1 commit