group transport components into individual bazel targets

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When modifying code in src/mongo/transport in such a way that dependencies change, it would be cleaner to have one bazel target per translation unit.

      This ticket is the work of doing that and updating all dependent targets.

      It might still be convenient to define targets composed of groups of the refactored targets, to simplify the dependencies of dependent targets. Or not.

            Assignee:
            Unassigned
            Reporter:
            David Goffredo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: