• G
    Fixed legacy storage renaming code · 7a7948e6
    Gabriel Mazetto 提交于
    During a previous refactor on project model, code related to the
    hashed storage was extracted into AfterRenameService, see
    4b9c17f1.
    
    The "path_before" was changed from using `previous_changes['path']` to
    `path_was`. They are not equivalent. `path_was` exists reliably only
    *before* persisting to the database. After database persistence is
    confirmed, the value is moved to `previous_changes[:attribute_name]`.
    
    Because the repository/attachments rename or storage upgrade happens
    after it was persisted to the database, we were in fact not informing
    the right parameters (and therefore not doing what it was supposed to).
    7a7948e6
after_rename_service_spec.rb 7.6 KB