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
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Hi all, I’m new here and would like to hear peoples views on my Elixir/Phoenix based game-engine! :smiley:
Mutonex gamedesign was finish...
New
Hello
I’ve been coding in Elixir for almost two years now because of my current job where we implemented Elixir in our application. But ...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
In 2021 I started a new library called Tempo with the objective of modelling time as a set of intervals - not as instants. In 2022 I gave...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex










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!