The current logging is not user friendly. Any plan for supporting Slf4j in future?

In my understanding the only current logging option is to get a Logger instance from ExecutionContext. we have to pass this logger instance onto any dependency method incase we want to add more loggings in dependent methods too. Also java.util.Logger is an older way to manage logs in java application which is not user friendly.
Here is a link - (https://stackoverflow.com/questions/11359187/why-not-use-java-util-logging)

slf4j(https://www.slf4j.org/) is a nice framework to manage logs in a user friendly way.Its also supports a better and user friendly string substitution for logs (https://www.slf4j.org/api/org/slf4j/helpers/MessageFormatter.html)

Is there any plan for supporting slf4j in future?

Ideally if Azure java functions can support lombook(@Slf4j) as first class citizen , we can annotate function and other classes with @Slf4j and rest of the logging is really easy to follow, rather than deriving Logger from ExecutionContext and passing it everywhere.

Let me know your thoughts.

まず、ExecutionContext のロギングエントリポイントと、その Logger が依存関係のメソッドにどのように渡されるかを確認します。現在の java.util.Logger のアプローチを、要求されている SLF4J および Lombok のサポートと比較します。完了条件は、合意された統合設計と、今後のロギングサポートに関する文書化された範囲が用意されていることです。

索引モデルが issue の本文から書いたものです。