Under that language's page, we can switch between old and new programming model snippets using tabs at the top of the snippet.
On the other hand, durable docs use those tabs on top of snippets to switch between programming languages with no pivot at the top:
We would have to add a tab for each of JS old model, TS old model, JS new model, TS new model, or switch all of the durable docs to using pivots at the top to choose a language rather than tabs, and reserve tabs for switching between models, or come up with another solution.
Same as https://github.com/Azure/azure-functions-nodejs-worker/issues/651 but for Durable docs. Durable docs do their organization of language snippets differently than other docs. For example, Blob storage bindings docs have a pivot at the top to choose a language:
Under that language's page, we can switch between old and new programming model snippets using tabs at the top of the snippet.
On the other hand, durable docs use those tabs on top of snippets to switch between programming languages with no pivot at the top:
We would have to add a tab for each of JS old model, TS old model, JS new model, TS new model, or switch all of the durable docs to using pivots at the top to choose a language rather than tabs, and reserve tabs for switching between models, or come up with another solution.