Qqwy
TypeCheck Core Team
Hello Everyone,
I am working on a small Phoenix/Ecto project. One of the features of this application is going to be that people can upload images. Right now I am using arc (and arc_ecto) to make the uploading procedure easier.
However, I want to store the dimensions and other metadata of the image that has been saved in the database as well, to make it nicer to display it in a gallery later.
I know there are multiple packages on Hex.pm that allow you to do this, such as fastimage, but these libraries work with a pathname to the file.
- Exactly how can I make a library that takes a pathname consume a
%Plug.Upload{}struct? I believe it contains a:pathfield, but I have been unable to build a%Plug.Upload{}manually to try it out. There is documentation of Plug.Upload, but it is rather short and uninformative (does the:pathfield include or exclude the actual filename itself, or only its folder? How do you make a%Plug.Upload{}struct manually?). - Related to this: How can you test file-uploading code? I am interested in doing both a feature-test, testing only if when you have a file if the dimensions are read and added to the changeset properly, and a full-stack test where a file is selected from the browser and it is then attempted to be uploaded.
Any help is greatly appreciated!
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Latest Phoenix Threads
Latest on Elixir Forum
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #iex
- #elixirconf-us
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Qqwy
All right! I have since learned that the
:pathfield is a path to a temporary file (including the filename itself). The:filenameis the name used during uploading, which can be used to do (a weak form of!) MIME-checking, and possibly to store it in your app, etc.I was able to call ImageMagick using the extracted
:path. (Yes, this code should be cleaned up and get some documentation, but it’s a proof-of-concept.)In my Phoenix 1.3 changeset function I’ve added a call to this function to the pipeline:
This works!
What I am yet to figure out though, is how this code can be tested properly. Please help!
OvermindDL1
I’d hardcode a known file in the project somewhere, create a custom
%Plug.Upload{}with the proper:pathset, then just call it and test the output.arkgil
IIRC, when I was working with file uploads in tests, I was creating
Plug.Uploadstruct manually and passed it as regular parameter toget,postetc. macros in controller tests:EDIT: but of course the question is about changesets
I think @OvermindDL1 is with the right approach.
StefanHoutzager
Maybe validity of path + filename have to be checked also? I’m still struggling with the when and how of unit tests.
http://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf
http://rbcs-us.com/documents/Segue.pdf
axelclark
I’m trying to test a file upload in my controller test. I’m using the approach you recommended:
but I keep getting the following error:
Here is my code:
I read the Phoenix.Params docs, but couldn’t figure out how to fix the error from the docs. Any ideas how to fix it? Thanks!
josevalim
When you do it as
post(conn, table_upload_path(conn, :create, table_upload: params)), you are passing the parameters as part of the query string, i.e. as part of the URL. You need to pass it as part of the post:axelclark
Good to go after the update, thanks!