-
Handle Route#name being nil after an update · 9bf9e6ebRobert 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.
9bf9e6eb
×