Actually generating the Abstractions package might be a good idea, I …

…guess..
sdcondon · Apr 11, 2021 · 491bd2d · 491bd2d
1 parent 2c8d038
commit 491bd2d
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 2 deletions.
diff --git a/.gitignore b/.gitignore
@@ -1,5 +1,6 @@
 # VS is determined to drop XML doc files alongside the source as well as in the target dir..
 FlUnit.xml
+FlUnit.Abstractions.xml
 
 ## Ignore Visual Studio temporary files, build results, and
 ## files generated by popular Visual Studio add-ons.

diff --git a/README.md b/README.md
@@ -64,9 +64,9 @@ Cons
   - Perhaps `ThenOfOutcome(o => o.Result.ShouldBe..)` and `ThenOfGiven1(g => g.Prop.ShouldBe..)` for succinctness? Though lambda discards work pretty well (to my eyes at least)..
   - We might have test cases where the prereqs aren't independent. E.g. allowing for: 
     ```
-    public static Test SumOfEvenAndOdd => TestThat
+    public static Test SumOfOddAndAdjacentEven => TestThat
       .GivenEachOf(() => new[] { 1, 3, 5 })
-      .AndEachOf(x => new[] { x - 1, x, x + 1 })
+      .AndEachOf(x => new[] { x - 1, x + 1 })
       ...  
     ```
     ..of course, people can generate these themselves in a single `GivenEachOf`, but supporting it as separate clauses might be handy. Maybe.

diff --git a/src/FlUnit.Abstractions/FlUnit.Abstractions.csproj b/src/FlUnit.Abstractions/FlUnit.Abstractions.csproj
@@ -3,6 +3,12 @@
   <PropertyGroup>
     <TargetFramework>netstandard2.0</TargetFramework>
     <RootNamespace>FlUnit</RootNamespace>
+    <GeneratePackageOnBuild>true</GeneratePackageOnBuild>
+	<Description>Abstractions for FlUnit.</Description>
+  </PropertyGroup>
+
+  <PropertyGroup>
+    <DocumentationFile>FlUnit.Abstractions.xml</DocumentationFile>
   </PropertyGroup>
 
 </Project>