Is your feature request related to a problem? Please describe.
Currently, the export_function/4 code action on unused functions always adds a new -export([some_fun/0]) module attribute. Which is totally fine from a functional perspective.
However I prefer the -export([[Name1/Arity1, ..., NameN/ArityN]). style of doing exports thus I catch myself manually merging the generated exports into a single export all the time.
Describe the solution you'd like
Alternatively create a new -export() or add the unused function to an existing -export().
Additional context
From my limited experience there are many -export() styles and of course all of this is highly subjective. An implementation satisfying all possible scenarios just add lots of accidental complexity. However I think a simple implementation like either add a new export or add it to "last" existing export would suffice and still be helpful.
Is your feature request related to a problem? Please describe. Currently, the
export_function/4
code action on unused functions always adds a new-export([some_fun/0])
module attribute. Which is totally fine from a functional perspective.However I prefer the
-export([[Name1/Arity1, ..., NameN/ArityN]).
style of doing exports thus I catch myself manually merging the generated exports into a single export all the time.Describe the solution you'd like Alternatively create a new
-export()
or add the unused function to an existing-export()
.Additional context From my limited experience there are many
-export()
styles and of course all of this is highly subjective. An implementation satisfying all possible scenarios just add lots of accidental complexity. However I think a simple implementation like either add a new export or add it to "last" existing export would suffice and still be helpful.I did a quick experiment here.
Happy to hear your opinion on this and I hope my remarks make sense. Thank you for for
erlang_ls
and have a nice day :+1: