• Gabriel Mazetto's avatar
    Refactored AfterRenameService to reduce coupling · d391dfb4
    Gabriel Mazetto authored
    We still rely on the Dirty API for project rename (before/after) values,
    but we don't access the dirty api from the service class anymore.
    
    The previous value is now part of the initialization, which makes it
    easier to test and the behavior is clearer.
    
    The same was done with the `rename_repo` on the Storage classes, we now
    provide before and after values as part of the method signature.
    d391dfb4
rename_reserved_project_names_spec.rb 1.85 KB