Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-3344

Allow TransactionOptions to take the enum equivalent values for its properties

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 1
    • Not Needed

      Use Case

      As a driver user I want a simple UX when using the transaction API.
      We should allow for example, readConcern: 'local' in the TransactionOptions to provide an easy to use user interface that matches the rest of our operations API.

      Dependencies

      • Our type definitions and API for TransactionOptions (not breaking, additive)

      Unknowns

      • n/a

      Acceptance Criteria

      Implementation Requirements
      • Add code that translates the enum values to the class proper at the public API level.
      • Change the type definition to accept the enum values.
      Testing Requirements
      • Add type tests and unit tests to make sure both the class proper and enum values are accepted
      Documentation Requirements
      • n/a
      Follow Up Requirements
      • n/a

            Assignee:
            durran.jordan@mongodb.com Durran Jordan
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Daria Pardue
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: