Yes, I can see that call(conn, {:error, :not_found}) will be called when {:error, :not_found} is somehow returned 
But cant cant figure out when that would happen, cant see any scenario when anyone would return {:error, :not_found}
theagilecoder
0
theagilecoder
Phillipp
Weird, I mostly do exactly that because all of my previous Phoenix applications had no database and therefore I simply return {:error, :not_found} when something isn’t found (e.g. state stored in a file or when trying to call a GenServer related to a specific subject which could possibly not exist yet).
1
LostKobrakai
For me it’s useful because I don’t like controllers raising intentionally. Exceptions imo should not be used for control flow and not finding an item in the db for a supplied id is nothing exceptional nor unexpected.
3
theagilecoder
Not weird. I was talking about the default files generated by the mix phx.gen.json generator not returning {:error, :not_found}. You can choose to edit and return whatever you want.
0
Phillipp
But I see no problem when the default files cover a very common pattern. Just because someone prefers to not use them, doesn’t mean they should not be generated.
1
theagilecoder
I also see no problem. My post was not about removing them in default scenario, it was about finding out who was calling it in the default scenario. Wether to keep it or remove it is above my pay grade.
0
lpil
Creator of Gleam
You’ve edited this post now, but I was still sent an email with the original message and it was very rude and unpleasent to recieve.
Please try to remember that the people you are talking to on the internet are people, you should treat them with courtesy, especially if they are taking time out of their day to help you with your problem.
11