Logger.warn/2 is deprecated

Phoenix Forum Questions / Help
,
1

Dear all tim,

I don’t know to solved this warning when try make mix test,
this is the code i get

==> tailwind
Compiling 3 files (.ex)
    warning: Logger.warn/1 is deprecated. Use Logger.warning/2 instead
    │
 72 │       Logger.warn("""
    │              ~
    │
    └─ lib/tailwind.ex:72:14: Tailwind.start/2

    warning: Logger.warn/1 is deprecated. Use Logger.warning/2 instead
    │
 86 │         Logger.warn("""
    │                ~
    │
    └─ lib/tailwind.ex:86:16: Tailwind.start/2

Generated tailwind app

I am using :

  • Windows 11
  • Elixir 1.16.3
  • Phoenix 1.7.12
  • Erlang OTP 26
2

You can resolve that exactly like the warning suggests you to, use Logger.warning/* instead of Logger.warn/*.

2 Likes
3

You can resolve that exactly like the warning suggests you to, use Logger.warning/* instead of Logger.warn/* .

tks Brother @NobbZ I almost forgot that, perhaps my brain need rest LOL

4

The warning is from a library (Tailwind).

It was fixed in January and it looks like Jose tagged a release a few days ago but it hasn’t been published to Hex yet for some reason.

You can ignore this warning though, it’s just a deprecation warning. It will be fixed eventually.

2 Likes
5

Tks Brother @garrison for the update news

1 Like
6

Oooof, I assumed this was their own code and just carried that name (tailwind) coincidally… I usually do not care for warning not from my own code and again assumed no one else did…

2 Likes
7

I know what you mean with treating them differently. I go on the cautious side and think when you depend on some code it becomes your code (i.e. need to care about security, correctness, performance, etc of third-party code and how it affects your project).

In this particular case, a call to the deprecated Log.warn will only become a real problem once, if ever, the method is removed. The general solution is indeed working with the maintainers of the dependency to have it updated (should be solved in a future release), or if that is not possible you can fork the dependency and fix it in your fork.

1 Like