Replies: 3 comments 5 replies
-
That's a possibility. The implementation for matching file types is far from complete or exhaustive but it wouldn't be too hard to generalise is and add something to the API. The api would need to support pathnames and binaries so that in-memory images can be processed. I'm curious what the use case is? Related to MIME types maybe? |
Beta Was this translation helpful? Give feedback.
-
|
I've caught up with the slack conversation now. Overall, it seems to me that https://github.com/Group4Layers/ex_image_info does a really good job of this. I'd be happier to contribute a PR to detect |
Beta Was this translation helpful? Give feedback.
-
|
I'll work on this for the next release (likely 0.54) over the next couple of weeks. I also want to investigate whether I can include some image safety aspects as well. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This library seems to do every possible thing with images but one simple thing: get the format of an image. In the introspection functions, I would love to see a function named sth. like
typethat would return "png" or "jpeg" or "heis", etc.It seems that you already parse the magic numbers in the
openfunctions. Would you consider extracting the magic numbers to be able to just check if an image file is of a given type? Given the scope of this library it does not feel right to add another library to my project just to check for that.Beta Was this translation helpful? Give feedback.
All reactions