You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warning: implicit hook found: lein-protoc.plugin/hooks
Hooks are deprecated and will be removed in a future version.
Warning: implicit hook found: lein-dotenv.plugin/hooks
Hooks are deprecated and will be removed in a future version.
Nothing I personally can do about these except hope the plugins get fixed before they stop working. It would be nice to ignore the warnings in the meantime. Is this possible? (This is a pretty common feature in other build tools -- maybe I've missed it here.)
The text was updated successfully, but these errors were encountered:
I'm on 2.9.1 (Linux Mint 20 apt-get). Just upgraded but I still see it so I assume my version is behind.
However, this question is more general than that -- I assume that warnings like this will come up from time to time in various dependencies (as they have in every project I've ever been on), and it's handy to ignore the ones you have explicitly decided not to fix.
Ah sure. You can export `LEIN_SILENT` to suppress warnings.
Most of the remaining warnings come from things that are directly in
your control in project.clj; other than that we only have warnings for
calling functions which are deprecated; in those cases it's usually easy
to send a PR which calls the new function if a plugin hasn't been
updated yet.
Thinking about this more, I would accept a patch for a way to supply a regex for silencing warnings. It would probably be best as an environment variable, since warnings can happen before profiles are parsed.
I get the following warnings on most
lein
tasks:Nothing I personally can do about these except hope the plugins get fixed before they stop working. It would be nice to ignore the warnings in the meantime. Is this possible? (This is a pretty common feature in other build tools -- maybe I've missed it here.)
The text was updated successfully, but these errors were encountered: