First of all, I like the idea and appreciate @Aduril sharing a suggestion.
Yes, the same thing can be achieved in many other ways - but I don’t think that’s the point here.
People new to elixir & phoenix learn about the great syntax and readability.
There is real value in being able to scan and understand code quickly. Pipes do help a lot there. So the idea is good!
Think of it this way: A language and framework should be consistent and predictable. The LiveView functions are something of a special case here. A plug or controller don’t return {:halt, conn} or {:ok, conn}, do they? No, you pipe your conn all the way through.
The best solution for me would be if the @impl functions like mount and handle_* would do the “reply magic” in the Phoenix.LiveView macro on their own.
I see no point in typing {:noreply, socket} in every LiveView because it adds no functionality and no value. (therefore it shouldn’t be in every LiveView you write)
It’s just something you have to explain every time you show LiveView to someone coming new to phoenix.
