Skip to content

Commit d997829

Browse files
committed
fix validation errors
1 parent 0624a1e commit d997829

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-functions/functions-add-output-binding-azure-sql-vs-code.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ In Functions, each type of binding requires a `direction`, `type`, and a unique
123123

124124
Open the *HttpExample.cs* project file and add the following `ToDoItem` class, which defines the object that is written to the database:
125125

126-
:::code language="csharp" source="~/functions-sql-todo-sample/ToDoModel.cs" range="6-16":::
126+
:::code language="csharp" source="~/functions-sql-todo-sample/ToDoModel.cs" range="6-16":::
127127

128128
In a C# class library project, the bindings are defined as binding attributes on the function method. The *function.json* file required by Functions is then auto-generated based on these attributes.
129129

@@ -504,7 +504,7 @@ def test_function(req: func.HttpRequest, toDoItems: func.Out[func.SqlRow]) -> fu
504504

505505
1. After deployment completes, you can again use the **Execute Function Now...** feature to trigger the function in Azure.
506506

507-
1. Again [check the data written to your Azure SQL Database](#verify-that-information-hase-been-written-to-the-database) to verify that the output binding again generates a new JSON document.
507+
1. Again [check the data written to your Azure SQL Database](#verify-that-information-has-been-written-to-the-database) to verify that the output binding again generates a new JSON document.
508508

509509
## Clean up resources
510510

0 commit comments

Comments
 (0)