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.

Empiece revisando el punto de entrada del registro de ExecutionContext y cómo se pasa su Logger a los métodos de las dependencias. Compare el enfoque actual basado en java.util.Logger con la compatibilidad solicitada para SLF4J y Lombok. El trabajo se considerará completado cuando exista un diseño de integración acordado y un alcance documentado para la compatibilidad futura con el registro.

Escrito por el modelo de indexación a partir del texto del issue.