Don't allow change streams to be used as emitters and iterators concurrently

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Needed
    • None
    • None
    • None
    • None
    • None
    • None

      We should throw some sort of error to the user if they attempt to use the change stream both as an event emitter, and iterate it using next/hasNext, etc.

              Assignee:
              Warren James (Inactive)
              Reporter:
              Matt Broadstone
              None
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: