cd-slash
I’ve come across a few instances recently where the built-in formatter is breaking otherwise working code. As an example, take a Phoenix component with a moderately long default string attribute:
attr :text_color, :string, default: "text-gray-900 hover:text-primary-700 dark:text-gray-400 dark:hover:text-white"
attr :border, :string, default: "border focus:outline-none"
def button(assigns) do
end
This code works fine, except that with default settings the text_color attribute gets broken into 2 lines and a new line added below:
attr :text_color, :string,
default: "text-gray-900 hover:text-primary-700 dark:text-gray-400 dark:hover:text-white"
attr :border, :string, default: "border focus:outline-none"
def button(assigns) do
end
The additional line between the two attr/3 statements breaks the component and results in a compiler error.
I’ve worked around this by adding line_length: 120 to my .formatter.exs file, but this is not an ideal workaround. I’m struggling to find a way to override the rule that’s causing this to break; can it be set to ignore attr/3 line length, for example, or even not apply the rule in this file type?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
Newlines shouldn’t be a problem. E.g. the CoreComponents phoenix generates do have such
attrdefintions as well and I’ve not seen anyone have problems with that. By my understandingattrsimply aggregates allattrinvokations between functions, no matter the whitespace or other (valid) syntax between the individualattrcalls.If that’s a problem on your end I’d argue that’s a bug somewhere, not a problem with the formatter.
Can you post the error you’re getting?
dimitarvp
This absolutely is not a compiler error, can you post the error you are getting? Which would have been helpful in your first post, it helps us assist with less back and forth.
cd-slash
You’re completely right, I seem to have made an error elsewhere and somehow thought it was a compiler error. My mistake, thanks for your inputs!