[jira] [Created] (LOG4J2-2432) Make `namedLogger` more discoverable

["Raman Gupta (JIRA)" <ji...@apache.org>]

Raman Gupta created LOG4J2-2432:
-----------------------------------

             Summary: Make `namedLogger` more discoverable
                 Key: LOG4J2-2432
                 URL: https://issues.apache.org/jira/browse/LOG4J2-2432
             Project: Log4j 2
          Issue Type: Improvement
          Components: Kotlin API
    Affects Versions: Kotlin 1.0.0
            Reporter: Raman Gupta


Currently, when instantiating a logger by name instead of by object (such as when not in the scope of an object e.g. a top-level function), one has to use `namedLogger(name)`. This is not very discoverable -- the user will simply get a "not found" error on `logger`, with no hints or IDE feedback on what to do or why `logger` cannot be found.

A better approach is to rename the `namedLogger` function to simply `logger`. When it is called within an Object without a parameter, the extension function will be used. When it is called with a parameter, whether inside or out, the named logger will be created. This is discoverable as the user's IDE will prompt for the missing `name` parameter when used from a top-level function, as in this scope only the named function is valid.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)