Merging dev into master #105

Author: Connor McMahon

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,57 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is. Please make an effort to fill in all the sections below; the information will help us investigate your issue.
+
+**Investigative information**
+
+- Durable Functions extension version:
+- durable-functions npm module version:
+- Language (JavaScript/TypeScript) and version:
+- Node.js version:
+
+***If deployed to Azure App Service***
+
+- Timeframe issue observed:
+- Function App name:
+- Function name(s):
+- Region:
+- Orchestration instance ID(s):
+
+> If you don't want to share your Function App name or Functions names on GitHub, please be sure to provide your Invocation ID, Timestamp, and Region - we can use this to look up your Function App/Function. Provide an invocation id per Function. See the [Functions Host wiki](https://github.com/Azure/azure-webjobs-sdk-script/wiki/Sharing-Your-Function-App-name-privately) for more details.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+> While not required, providing your orchestrator's source code in anonymized form is often very helpful when investigating unexpected orchestrator behavior.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Actual behavior**
+A clear and concise description of what actually happened.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Known workarounds**
+Provide a description of any known workarounds you used.
+
+**Additional context**
+
+- Development environment (ex. Visual Studio)
+- Links to source
+- Additional bindings used
+- Function invocation IDs

README.md

@@ -1,3 +1,8 @@
+|Branch|Status|
+|---|---|
+|master|[![Build Status](https://azfunc.visualstudio.com/Azure%20Functions/_apis/build/status/Azure.azure-functions-durable-js?branchName=master)](https://azfunc.visualstudio.com/Azure%20Functions/_build/latest?definitionId=13&branchName=master)|
+|dev|[![Build Status](https://azfunc.visualstudio.com/Azure%20Functions/_apis/build/status/Azure.azure-functions-durable-js?branchName=dev)](https://azfunc.visualstudio.com/Azure%20Functions/_build/latest?definitionId=13&branchName=dev)|
+
 # Durable Functions for Node.js
 
 The `durable-functions` npm package allows you to write [Durable Functions](https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-overview) for [Node.js](https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-node). Durable Functions is an extension of [Azure Functions](https://docs.microsoft.com/en-us/azure/azure-functions/functions-overview) that lets you write stateful functions and workflows in a serverless environment. The extension manages state, checkpoints, and restarts for you. Durable Functions' advantages include:
@@ -64,7 +69,7 @@ module.exports = df.orchestrator(function*(context){
 
 **Note:** Orchestrator functions must follow certain [code constraints.](https://docs.microsoft.com/en-us/azure/azure-functions/durable-functions-checkpointing-and-replay#orchestrator-code-constraints)
 
-7. Write your client function ([see sample]((./samples/HttpStart/))):
+7. Write your client function ([see sample](./samples/HttpStart/)):
 ```javascript
 module.exports = async function (context, req) {
     const client = df.getClient(context);
@@ -116,4 +121,4 @@ The `durable-functions` shim lets you express a workflow in code as a [generator
 
 These calls return a `Task` or `TaskSet` object signifying the outstanding work. The `orchestrator` method appends the action(s) of the `Task` or `TaskSet` object to a list which it passes back to the Functions runtime, plus whether the function is completed, and any output or errors.
 
-The Azure Functions extension schedules the desired actions. When the actions complete, the extension triggers the orchestrator function to replay up to the next incomplete asynchronous unit of work or its end, whichever comes first.
+The Azure Functions extension schedules the desired actions. When the actions complete, the extension triggers the orchestrator function to replay up to the next incomplete asynchronous unit of work or its end, whichever comes first.

azure-pipelines.yml

@@ -0,0 +1,32 @@
+variables: {
+  MODULE_VERSION: '1.2.2',
+  NODE_LOWER_LTS: '8.x',
+  NODE_HIGHER_LTS: '10.x'
+}
+name: $(MODULE_VERSION)-$(Date:yyyyMMdd)$(Rev:.r)
+
+trigger:
+- master
+- dev
+
+jobs:
+- job: UnitTests
+  strategy:
+    matrix:
+      WINDOWS_NODE8:
+        IMAGE_TYPE: 'vs2017-win2016'
+        NODE_VERSION: $(NODE_LOWER_LTS)
+      WINDOWS_NODE10:
+        IMAGE_TYPE: 'vs2017-win2016'
+        NODE_VERSION: $(NODE_HIGHER_LTS)
+  pool:
+    vmImage: $(IMAGE_TYPE)
+  steps:
+  - task: NodeTool@0
+    inputs:
+      versionSpec: $(NODE_VERSION)
+    displayName: 'Install Node.js'
+  - script: npm install
+    displayName: 'npm install'
+  - script: npm run test
+    displayName: 'npm build and test'