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.

Iniziate esaminando il punto di ingresso del logging di ExecutionContext e il modo in cui il suo Logger viene passato ai metodi delle dipendenze. Confrontate l’approccio attuale basato su java.util.Logger con il supporto richiesto per SLF4J e Lombok. Il lavoro sarà considerato completato quando saranno disponibili un design di integrazione concordato e un ambito documentato per il futuro supporto al logging.

Scritto dal modello di indicizzazione a partire dal testo della issue.