BigW Consortium Gitlab

  1. 07 Jun, 2017 1 commit
  2. 12 May, 2017 1 commit
  3. 05 May, 2017 6 commits
  4. 21 Mar, 2017 1 commit
  5. 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.
  6. 08 Feb, 2017 2 commits
  7. 25 Jan, 2017 1 commit
  8. 13 Jan, 2017 1 commit
  9. 19 Dec, 2016 1 commit
  10. 08 Dec, 2016 1 commit