Version 3

This issue will track all work related to our next major release. You can try out v3 by installing directly from github (npm install Azure/azure-cosmos-js#v3 or the next tag on npm (npm install @azure/cosmos@next). The below list isn’t in any particular order. Some of the items are blocked, are stretch goals, or may have already been completed. Anything marked as a stretch goal will not block the v3 release. No specific release date has been set.

• Move to browser friendly HTTP internals using cross-fetch (Steve)
• Implement request pipeline customization, bringing inline with .NET SDK (Chris)
• Change response types to classes (BREAKING, Chris, Next Task)
• Force setting partition key. In the near future, Cosmos will require them. (BLOCKED. Waiting on backend changes)
• Add Change Feed Processor (BLOCKED. Stretch Goal, will not block V3 release)
• Additional logging (Chris, possibly going in v2 first and ported to v3)
• Add code coverage (Stretch goal)
• Enable offer tests/code (Chris, v2+v3)
• Proxy via Agent (Steve, COMPLETE)
• Enable no-unnecessary-classes (Steve, COMPLETE)
• Enable parallel tests (Steve)
• Split test/src into TS projects with references and enable noUnusedVariables (Steve)
• Require method return types (linting)
• Add internal flag for type defs
• Header name changes (BLOCKED by backend)
• Add Cancellation tokens. Will be easy to support with fetch (#193)
• 404 should not throw for reads #203 (Chris)
• Remove next/current from query in favor or paginated results
• Run tests against browser again in CI (Steve)

[tony-gutierrez]

Direct mode?

[southpolesteve]

Closing this issue since v3 is out and the list is fairly stale

@antempus @tony-gutierrez I’ll continue any direct mode discussion over in #47