brkn
Elixir script file without extension is ignored by `mix format`
My env and context
- Elixir 1.19.1
- Erlang 28.1.1
- Editor: vscodium (Basically same as vscode)
- Vscodium Extension: ElixirLS v0.30.0
- Not sure if it matters: zsh, macos arm
- I’m a beginner in elixir and beam
My problem
I have a language agnostic repo, and I’m trying to get my editor to format my script files.
Example scripts/upcase
#!/usr/bin/env elixir
case System.argv() do
[] -> IO.read(:stdio, :all)
args -> Enum.join(args, " ")
end
|> String.upcase()
|> IO.puts()
When I open this file on my editor, it detects the language and syntax highlights correctly but format file command doesn’t work.
So I thought I could do it via mix format but that didn’t work either, silently exits without formatting.
What I tried
mix format scripts/upcaseis silently exiting, no changes.- Could it be because my lang agnostic repo doesn’t have
.formatter.exsfile?mix format –-dot-formatter ~/.formatter.exs scripts/upcase-
❯ cat ~/.formatter.exs [ inputs: ["scripts/upcase"] ] - still silently exiting, file is not changed.
- After reading the mix format docs carefully, I realized I can pipe string into
mix format --
mix format - < scripts/upcase > /tmp/temp && mv /tmp/temp scripts/upcase -
Yes this works, but it’s very clunky.
-
Why could this be?
So I dived into the source, and I think this block is the culprit
defp find_formatter_for_file(file, formatter_opts) do
# ...
cond do
# ...
ext in ~w(.ex .exs) ->
&elixir_format(&1, [file: file] ++ formatter_opts)
true ->
& &1
end
# ...
end
Can I create a formatter plugin for extensionless files?
I thought this could be a solution, but I am not sure what’s the best way to do this since elixir_format/2 is a private method, see on github.
Should I copy the method’s body, and use Code.format_string!/2 ?
First Post!
Eiji
I would not recommend writing Elixir scripts without extension. I understand that you don’t want to type .exs, but you can create a shell aliases for such cases. You can even write a simple look that would iterate all of your projects, enter the scripts directory, read files and create alias for each of them. In my opinion that the best you can do.
However it’s not the limit of your possibilities. If you are fine with a workaround then you can add a custom plugin for your formatter.exs configuration. Such plugin can register itself to "" (empty string) as one of allowed extensions. Since Path.extname/1 returns empty string only if a string does not have extension your plugin should always work only for the scripts you wanted.
The rest is to call the standard formatter inside your plugin as you already did in your 3rd point in the shell.
For more information please take a look at the following documentation pages:
Last Post!
brkn
I know that I can copy, or even better create symlinks, but I would rather not.
It’s not impossible, vscode’s official typescript extension can handle this just fine. Try it yourself, it works for both unsaved editor or extensionless file.
#! /usr/bin/env node
console.log(
"white space is way off"
)
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #hex









