Don't require ReadPreferenceOptions for non-primary read preferences

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Unknown
    • 3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None

      We seem to always require users specify ReadPreferenceOptions when constructing a non-primary ReadPreference, even though there are no required options. It would be a little nicer to make the stored options Option<ReadPreferenceOptions>.

            Assignee:
            Isabel Atkinson
            Reporter:
            Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: