Check null dynamic defaults

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • next
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As Dan said, it seems like a lot of options can be:

      1. If the user provided them for this call, use them,
      2. Else if they set them on the mongoClient, use them
      3. Else consider the option non-existent, and use a static default

      We should be checking that dynamic defaults are not null before setting them in `options_validator`.

              Assignee:
              Unassigned
              Reporter:
              Katherine Walker (Inactive)
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: