During development, provide a mechanism to log in logv2 without providing a logid

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During development it's occasionally desirable to be able to cheaply sprinkle log messages into source code to aid in debugging (printf style debugging). logv2 makes this painful, by requiring logids for each message (requiring some kind of elaborate provisioning system for what previously could have been as inexpensive as copy/paste).

      If we could provide a special log macro, or allow a special logid, that was usable in local development and for patch builds (but not allowable through the commit queue) that would enable that use case, while still enforcing that log messages have ids in production builds.

              Assignee:
              DO NOT USE - Backlog - Dev Tools
              Reporter:
              Mira Carey
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: