ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: TypeScript
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a driver developer
      I want our packages to compile with TS 6.x,
      So that we can stay up-to-date with Typescript releases.

      User Experience

      • Each package owned by the node drivers team should be build cleanly on ES6, assuming no production code changes.

      Dependencies

      • None

      Risks/Unknowns

      • Given users consume our builds, there's a real chance that we build to a different module format or change the build output in a non-trivial way due to newly introduced features
      • Multiple tsconfig files are used throughout our packages, and are used in different contexts. Each of these need to be smoke tested

      Acceptance Criteria

      Implementation Requirements

      • Each repository which uses Typescript (mongodb-connection-string, mongodb-client-encryption, js-bson, node-mongodb-driver) should produce a bundle with near-parity to the original (exceptions allowed, assuming they're trivial and called out in the PR description)
      • Each repository should pass existing tests which are run in CI which rely on typescript
      • Existing tsconfig files should all be smoke tested 

      Testing Requirements

      • existing tests to be updated to support any changes which are a side-effect of ts6 update

      Documentation Requirements

      • Non-trivial diff's between main & the ts6 adoption branch (for each repo) should be justified and called out in each PR's description

      Follow Up Requirements

      • Packages which are blocked from updates should be noted as such

       

            Assignee:
            Unassigned
            Reporter:
            Bailey Pearson
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: