Configure Compatibility for Deprecation Rewrites

[maennchen]

Styles converts certain code like :timer.minutes(5) to newer versions like to_timeout(minute: 5), which is awesome.

Unfortunately it is less awesome for libraries that still support Elixir Versions older than the one running mix format and don't have the shiny new functions that the code is being converted to.

I would love if we could implement a config that lets you set a version requirement (or take the one from mix.exs) to decide if a rewrite should be enabled or not.

[novaugust]

ah great point @maennchen, thanks for the issue. reckon that should've been a major semver bump when i added that feature.

i'll let this percolate in the back of my head and see what i can come up with. for now you can pin at 1.3.3 to avoid the to_timeout rewrites (or, sadly, just write the integer literals)

[emkguts]

If it's at all useful, I encountered this issue as well and decided to look at the mix.exs version to determine which rewrites to do. It might be more configuration than you're interested in supporting, but wanted to share in case it helps!
emkguts/quokka@60ad269

[maennchen]

@emkguts It looks like the quokka version extraction code is quite a bit more complicated than needed.

You should be able to run Mix.Project.config()[:elixir]. If you've not already loaded the config for some reason, you can use Mix.Project.in_project/4 for that.

[emkguts]

Thanks for the pointer! Just made use of it. 😄 🙏

[novaugust]

I'd be happy to take a PR for this if either of you feel inclined =)

[novaugust]

I think I'll implement this with as little logic as possible - no reading from mix project, just a user provided value to be parsed. I've worked on too many projects that don't bump the elixir version in mix and don't want to needlessly turn this off for those cases