-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can we remove the source_file from destination_name? #70
Comments
For instance I think |
It's a concatenation of source and name. Are there cases where a model would have multiple sources of derivative and they would have the same name here? For example: original_file_thumb and other_file_thumb. The path of both children would be the same if it weren't for the concat in that case. We could attach name as original_name to the file object. I think original name is nil or blank currently for the derivatives, as it is not passed through as an option to add_file. |
Looks like destination_name should remain with the source_file prefix even though that doesn't perfectly suit our current downstream use. I'm going to create an issue to pass the name of the directive responsible for the derivative (e.g. thumbnail) as the original_name on the derivative file that gets emitted to |
Is there any reason why destination_name needs to be a concatenation of source_file and derivative name when it gets set here?
I think it makes sense to have it just be the derivative name. The way this works now I have to strip out the source name in Hydra::Works.
The text was updated successfully, but these errors were encountered: