-
-
Notifications
You must be signed in to change notification settings - Fork 206
Fix Elixir 1.15 warnings #553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Elixir 1.15 warnings #553
Conversation
88d3084
to
751f4da
Compare
One tiny comment but otherwise LGTM! |
0cf619d
to
4928ac2
Compare
Elixir 1.15 hard-depcreates Logger.warn. Custom logger backends that still use the legacy custom backend API must translate the log level to avoid emitting a deprecation warning. Co-authored-by: José Valim <[email protected]>
4928ac2
to
591a000
Compare
@antonpirker @sl0thentr0py this is ready for review. |
Great work! Lots of Elixir 1.15 adoption, so it would be awesome to get this merged in 🙃 |
@mitchellhenke @michallepicki still with Sentry? |
Please get this released 🙏🏻 🙇🏻 It's our current 1.15.2 upgrade blocker 🙂 |
Couldn't agree more 😅 |
will set aside some time for elixir next week, promise! |
Sorry to be this guy but can we get a release for this? 😬 |
@anthonator don't be that guy... 😄 Just kidding. We merged this literally a few hours ago, we're working on a release, no worries! 🙃 |
😅 Sorry and thank you! 😅 |
Elixir 1.15 hard-depcreates Logger.warn/1. Custom logger backends that still use the legacy custom backend API must translate the log level to avoid emitting a deprecation warning. Co-authored-by: José Valim <[email protected]>
Elixir 1.15 hard-deprecates Logger.warn. Custom logger backends that still use the legacy custom backend API must translate the log level to avoid emitting a deprecation warning.
Fixes #552