• Type: Icon: Epic Epic
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • To Do
    • Operations Refactor

      How we currently run operations and build commands could be dramatically improved. This will be a living ticket for improvements. We could introduce classes to represent each operation and these could encapsulate most of the numerous arguments we currently pass around (cmd, sock_info, read_preference, read_concern, write_concern, etc...). Introducing classes can lead to better code reuse and more centralized error handling which is becoming more common (retryable reads/writes, transaction pinning).

            Assignee:
            Unassigned Unassigned
            Reporter:
            prashant.mital Prashant Mital (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: