Handle extensions from mime-type about carrierwave-base64 HOT 8 CLOSED

I'd like to see a solution to this too. Currently I'm having to inject a bogus application/extension content type into my base64 string just to get the extension I want.

I'd think something like this as an alternative would make sense as a default with an option to override it maybe.

MIME::Types['application/vnd.openxmlformats-officedocument.wordprocessingml.document'].first.preferred_extension #=> "docx"

from carrierwave-base64.

@adamcrown Thanks for looking into that. I'll try to take a stab at it this weekend.

from carrierwave-base64.

How about passing a name of the file in the payload with the upload?

from carrierwave-base64.

from carrierwave-base64.

@Quintasan @adamcrown I made a commit, that adds automatic identification of the file extension, using the content type from the uploaded base64 string: c93c690.

If you have time, I would like you to test it. If it's fine, I will release a 2.4.0 version, including this change.

from carrierwave-base64.

Ok, I think I can already release the 2.4.0

from carrierwave-base64.

@lebedev-yury Sorry I'm so very late to this. I've just now had time to revisit this issue. Just wanted to let you know that it's working great. Thanks.

If anybody else stumbles on this and wonders how to add custom mime types. The documentation isn't great for the mime-types gem, but this is what worked for me

MIME::Types.add(
  MIME::Type.new('application/icml').tap {
    |type| type.add_extensions 'icml'
  }
)

from carrierwave-base64.

@adamcrown thank you! I will add this information to the readme

from carrierwave-base64.