Merge pull request #329 from ServiceComposer/use-in-place-snippets

Use InPlaceOverwrite for snippets
ServiceComposer · Oct 9, 2021 · f615846 · f615846
2 parents d5d7a4f + 3c20568
commit f615846
Show file tree

Hide file tree

Showing 25 changed files with 2 additions and 390 deletions.
diff --git a/.github/workflows/run-markdownsnippets.yml b/.github/workflows/run-markdownsnippets.yml
@@ -9,7 +9,7 @@ jobs:
     - name: Run MarkdownSnippets
       run: |
         dotnet tool install --global MarkdownSnippets.Tool
-        mdsnippets ${GITHUB_WORKSPACE}
+        mdsnippets ${GITHUB_WORKSPACE} -c InPlaceOverwrite
         git add .
       shell: bash
     - name: Fix links

diff --git a/README.md b/README.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /README.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 <img src="assets/ServiceComposer.png" width="100" />
 
 # ServiceComposer

diff --git a/README.source.md b/README.source.md
diff --git a/docs/README.md b/docs/README.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/README.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # ASP.NET Core 3.x and .NET 5
 
 Starting ASP.NET Core 3.x ServiceComposer leverages the new Endpoints support to plugin into the request handling pipeline.

diff --git a/docs/README.source.md b/docs/README.source.md
diff --git a/docs/action-results.md b/docs/action-results.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/action-results.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # ASP.Net MVC Action results
 
 MVC Action results support allow composition handlers to set custom response results for specific scenarios, like for example, handling bad requests or validation error thoat would nornmally require throwing an exception. Setting a custom action result is done by using the `SetActionResult()` `HttpRequest` extension method:

diff --git a/docs/action-results.source.md b/docs/action-results.source.md
diff --git a/docs/asp-net-core-2x/README.md b/docs/asp-net-core-2x/README.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/asp-net-core-2x/README.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # ASP.NET Core 2.x
 
 _NOTE: As of v1.8.0 ASP.NET Core 2.x is legacy. It'll be removed in v2.0.0, consider moving to the new endpoint and attribute routing based approach available starting with ASP.NET Core 3.x._

diff --git a/docs/asp-net-core-2x/README.source.md b/docs/asp-net-core-2x/README.source.md
diff --git a/docs/authentication-authorization.md b/docs/authentication-authorization.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/authentication-authorization.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # Authentication and Authorization
 
 By virtue of leveraging ASP.NET Core 3.x Endpoints ServiceComposer automatically supports authentication and authorization metadata attributes to express authentication and authorization requirements on routes. For example, it's possible to use the `Authorize` attribute to specify that a handler requires authorization. The authorization process is the regular ASP.NET Core 3.x process and no special configuration is needed to plugin ServiceComposer:

diff --git a/docs/authentication-authorization.source.md b/docs/authentication-authorization.source.md
diff --git a/docs/composition-over-controllers.md b/docs/composition-over-controllers.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/composition-over-controllers.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # Composition over controllers
 
 ServiceComposer can be used to enhance a MVC web application by adding compostion support to Controllers. ServiceComposer can be configured to use a technique called "Composition over controllers":

diff --git a/docs/composition-over-controllers.source.md b/docs/composition-over-controllers.source.md
diff --git a/docs/custom-http-status-codes.md b/docs/custom-http-status-codes.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/custom-http-status-codes.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # Custom HTTP status codes in ASP.NET Core 3.x
 
 The response status code can be set in requests handlers and it'll be honored by the composition pipeline. To set a custom response status code the following snippet can be used:

diff --git a/docs/custom-http-status-codes.source.md b/docs/custom-http-status-codes.source.md
diff --git a/docs/custom-json-response-serialization-settings.md b/docs/custom-json-response-serialization-settings.md
@@ -1,15 +1,8 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/custom-json-response-serialization-settings.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # Custom JSON response serialization settings
 
 _Available starting with v1.8.0_
 
-By default each response is serialized using [Json.Net](https://www.newtonsoft.com/json/help/html/Introduction.htm) and serialization settings (`JsonSerializerSettings`) are determined by the [requested response casing](response-serialization-casing.md). If the requested casing is camel casing, the default, the folowing serialization settings are applied to the response:
+By default each response is serialized using [Json.Net](https://www.newtonsoft.com/json/help/html/Introduction.htm) and serialization settings (`JsonSerializerSettings`) are determined by the [requested response casing](response-serialization-casing.source.md). If the requested casing is camel casing, the default, the folowing serialization settings are applied to the response:
 
 <!-- snippet: net-core-3x-camel-serialization-settings -->
 <a id='snippet-net-core-3x-camel-serialization-settings'></a>

diff --git a/docs/custom-json-response-serialization-settings.source.md b/docs/custom-json-response-serialization-settings.source.md
diff --git a/docs/model-binding.md b/docs/model-binding.md
@@ -1,10 +1,3 @@
-<!--
-GENERATED FILE - DO NOT EDIT
-This file was generated by [MarkdownSnippets](https://github.com/SimonCropp/MarkdownSnippets).
-Source File: /docs/model-binding.source.md
-To change this file edit the source file and then run MarkdownSnippets.
--->
-
 # Model Binding
 
 _Available starting with v1.9.0_