Use Case

As a... Node.js user
I want... the cursor fluid API and options API to be consistent and equivalent
So that... I can confidently switch between them for whatever code flow serves me best

User Experience

• Assertions and validations performed inside chained methods should also apply to options usage

Dependencies

• None

Risks/Unknowns

• How will the change in assertions impact existing usage?
• How can we best share the validation for re-use
• When can/should we defer to server errors/validation?

Acceptance Criteria

Implementation Requirements

• Consolidate and test chainable method behavior and options behavior to be equivalent
• Ensure equivalent validations are performed for either usage
  • Address any order dependent options to be order agnostic (ex. tailable cursors can't have a sort, what happens when one is specified before the other?)

Testing Requirements

• Test every option that has an equivalent chain method results in the same validation and configuration of the cursor

Documentation Requirements

• https://jira.mongodb.org/browse/DOCSP-48707

Follow Up Requirements

• None