build(deps-dev): bump styler from 1.9.1 to 1.11.0

[dependabot]

Bumps styler from 1.9.1 to 1.11.0.

Release notes

Sourced from styler's releases.

v1.10.1: experimental refactoring tasks

Adds two experimental refactoring features as mix tasks.

mix styler.remove_unused

With Elixir 1.20 on the horizon, many projects are about to discover that they have a lot of unnecessary require Logger lines throughout their codebase.

mix styler.remove_unused will automate the removal of those unused require: statements, alongside any unused import: and unused alias: warnings.

This has long been an internal script useful for running after a bigger refactor that resulted in many superfluous aliases, but with 1.20 coming it seems it might be useful for others as well.

This will never be an integrated part of Styler's format plugin features, as it would not be correct to remove unused nodes whenever running format. It's typical to have unused warnings while in the midst of an implementation, and deleting that code would be obnoxious.

mix styler.inline_attrs <file>

Inlines one-off module attributes that define literal values.

This is something that sometimes is good, and sometimes is bad. In general, defining a module attribute when you could've just written an atom is bad, so inlining is good!

It would probably be most useful as a refactor ability for a language server, but CLIs are a nice second place.

An example of a situation where it results in an improvement:

# Unnecessary indirection with single-use literal-value module attributes
defmodule A do
  @http_client_key :http_key
  @default_client MyHTTPClient
def http_client, do: Application.get_env(:my_app, @​http_client_key, @​default_client)
end
Much better! styler.inline_attrs will perform this refactor
defmodule A do
def http_client, do: Application.get_env(:my_app, :http_key, MyHTTPClient)
end

It's worthwhile to run this on some suspicious files, then followup with manual intervention when it went too far. This style is not aware of quote boundaries, and so might do some broken things. (Hence "EXPERIMENTAL")

You've been warned =)

v1.10.0

Improvements

Two new standard-library pipe optimizations

• enum |> Enum.map(fun) |> Enum.intersperse(separator) => Enum.map_intersperse(enum, separator, fun)
• enum |> Enum.sort() |> Enum.reverse() => Enum.sort(enum, :desc)

And Req (the http client library) pipe optimizations, as detailed below

... (truncated)

Changelog

Sourced from styler's changelog.

1.11.0

Improvements

• mix styler.inline_attrs: Allow multiple file paths to be specified: mix styler.inline_attrs <file1> [<file2> ...]

Module Directive References

Module directives got smarter. Styler will no longer move module attributes below their references in use or @moduledocs.

In other words, Styler will leave the following code untouched:

defmodule MyGreatLibrary do
  @library_options [...]
  @moduledoc make_pretty_docs(@library_options)
  use OptionsMagic, my_opts: @library_options
end

1.10.1

Improvements

Adds two experimental refactoring features as mix tasks.

mix styler.remove_unused

With Elixir 1.20 on the horizon, many projects are about to discover that they have a lot of unnecessary require Logger lines throughout their codebase.

mix styler.remove_unused will automate the removal of those unused require: statements, alongside any unused import: and unused alias: warnings.

This has long been an internal script useful for running after a bigger refactor that resulted in many superfluous aliases, but with 1.20 coming it seems it might be useful for others as well.

This will never be an integrated part of Styler's format plugin features, as it would not be correct to remove unused nodes whenever running format. It's typical to have unused warnings while in the midst of an implementation, and deleting that code would be obnoxious.

mix styler.inline_attrs <file>

Inlines one-off module attributes that define literal values.

This is something that sometimes is good, and sometimes is bad. In general, defining a module attribute when you could've just written an atom is bad, so inlining is good!

It would probably be most useful as a refactor ability for a language server, but CLIs are a nice second place.

An example of a situation where it results in an improvement:

# Unnecessary indirection with single-use literal-value module attributes
defmodule A do
  @http_client_key :http_key
</tr></table> 

... (truncated)

Commits

• bb07d16 1.11.0
• f839aa6 module attributes: dont break references from use, moduledoc, etc
• a68788c fix inline_attributes task docs
• 5f6d2ba readme task link fix
• 02292c6 mix styler.remove_unused: allow multiple file args
• 4e013e0 v1.10.1
• 6055b07 Add mix styler.inline_attrs \<file> refactor tool
• 3e29cae Add experimental mix styler.remove_unused task
• 77861bf pipes docs reorganization
• ae19d31 bump version in changelog
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)