Skip to content

How skip behavior of destroying the previous file if it is updated #711

Description

@mariaLauraDev

In my application I have a class that inherits Shrine from the gem and I don't want it to have the behavior of destroying the previous file if it is updated, because this generates corruption in the path of the previous files that are still requested by my system, because it is stored in cache. Is there any method or configuration that I can declare in my class to avoid the behavior of the following screenshot?

image

My class that inherits shrine

class FontUploader < Shrine Attacher.validate do validate_extension_inclusion %w[ttf svg otf woff2] end end

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions