Ensure that existing events are tracked alongside a connectionId whenever relevant

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 1.43.5
    • Affects Version/s: None
    • Component/s: None
    • 3
    • Iteration Earth (Jun 17-Jul 1), Iteration Fortitudo
    • Not Needed
    • Developer Tools

      Not doing this might break telemetry from the usage perspective so we would want to do this as part of milestone-2.

      We should discuss the way to approach it, suggested solutions were:

      • typing events with / without connectionId and modifying places wherever needed
      • providing helper like useScopedLoggerAndTelemetry to do this transparently wherever applicable

            Assignee:
            Paula Stachova
            Reporter:
            Himanshu Singh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: