I have read the thread and I am not sure I can think of an “optimal” solution.
We could rename “checkbox” to “boolean”, but all other input types are named after their HTML counter-parts, not their types, so having this named “boolean” would be confusing in a different way. Perhaps “boolean_checkbox”. But those are all not optimal to justify changing the generators.
Similarly, we could change the name of the function, but I am not exactly sure it helpers either. <.inputs clearly do more than the regular <input, based on the fact it renders labels and everything else, so I am not sure if the name would make such a big difference. I assume the first instinct @gorghoa would have, regardless of the name, is to use whatever is provided.
Then there is the case of multiple checkboxes but then I think it deserves its own input type and I don’t think you can build on top of <.input type="checkbox"> anyway because you will likely make different assumptions regarding styling.
WIth all that said, it sounds like improved documentation is the best way to go about it. Perhaps a summary of HTML input types and their supported types.
EDIT: better docs here: Improve .input docs · phoenixframework/phoenix@b8fe141 · GitHub
. But seeing that that it doesn’t, I would have immediately reached to the documentaion. So, I also think that the documentation is a good place for disambiguation on this matter 
.
(even though the checkbox is really the exception).